Output:export
Unanswered
the wave posted this in #help-forum
the waveOP
I tried using docker to deploy my app and the only way I managed to do it is changing the config to output: export
Is that good? Bad?
What are the pros and cons of this approach
(I must say my docker deployment was way faster that way)
Is that good? Bad?
What are the pros and cons of this approach
(I must say my docker deployment was way faster that way)
41 Replies
basically it bundles your app into a spa
its like u would build a vanilla react app
every page is prebuilt and wont be rendered on the server
clientside only
@gin clientside only
the waveOP
is that better or worse performance wise?
but you are better off not using nextjs
@gin but you are better off not using nextjs
the waveOP
what would you recomend then?
with ssr off
but you will need to build a own api
and everything else that u cant leave open on the client
the waveOP
i need something that is good for simple small pages ,
i need to scale that as well so relatvly easy to work with
i dont come from js background , but when i started learning web it seemed like the best aproch
like my api is python anyways
i need to scale that as well so relatvly easy to work with
i dont come from js background , but when i started learning web it seemed like the best aproch
like my api is python anyways
if u only need a website that is fast and doesnt need a serverfull env then just use vanilla react or react router
but u will lack off every dynamic feature that can be done with node
the waveOP
hmmm like i am mustly building landers in my job, i heard svelt is good for that but i am not sure how much support does it have
svelte is also good
but react has the most support and libraries
for me: react recommended all the way
the waveOP
hmmmm dont i need a framework or something?
or is react a framework as well?
@the wave hmmmm dont i need a framework or something?
go with framework
react router makes it into a framework
no it exist a very long time
just the v7 is new
the waveOP
is it just not that popular?
it wasnt because everyone was using using nextjs or any other big meta framework
it was a library with some extra features enhancing react
but now its a framework too
if not nextjs, im using react router v7
the waveOP
basicly i need something that will be fast to deploy to a server (small in size) and with relativly good performance
i dont really need denamic capabilities
i dont really need denamic capabilities
(if things looks good then we are happy XD)
i liked next js because i can reuse componets and scale down the app size (somewhat)
You can reuse components in basically any front end framework, even vanilla React itself.
The easiest would be to start a project with Vite and React and plug a Router (like React Router) if you need multiple pages etc.
Next.js assumes you know React + you are familiar with Server Side rendering patterns. Also gives you so many cool features React lacks of (data fetching patterns, mutations, router built in, API route handlers)
Next.js assumes you know React + you are familiar with Server Side rendering patterns. Also gives you so many cool features React lacks of (data fetching patterns, mutations, router built in, API route handlers)