Closed 01026551290 closed 3 months ago
Tauri does not have a nodejs nor nextjs runtime in build mode but you still need one in standalone mode to run your nextjs app. The only difference between standalone and standard is that standalone inlines the node_modules dependency into the standalone bundle so that you don't have to install them on your server.
This is why we're always talking about output: export
in our docs. This will generate a (prerendered) static output that any standard http server can serve without a nodejs runtime.
If you need a running nodejs runtime, because you use features that are incompatible with output: export
you could sidecar your frontend instead, which of course will increase the bundle size and is not as straight forward (we don't have a guide for that, so you're a bit on your own)
Nextjs is moving the project based on the server, do you have any plans to support the server based project?
Not in the near future, no (i assume at some point we will). The whole idea of Tauri was to get rid of the nodejs runtime in webbased desktop apps.
Describe the bug
hi I'm basically doing a standalone build on nextjs, so when building .next/standalone is supposed to fall off. But I have a question here. When I run it on dev, the screen is coming out well, but I can't find the screen when building. What's the reason?
Reproduction
No response
Expected behavior
No response
Full
tauri info
outputStack trace
No response
Additional context
No response