You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the Next.js integration Doc, step 3 contains the configuration below. Next.js hot reload feature won't work properly.
// Configure assetPrefix or else the server won't properly resolve your assets.assetPrefix: isProd ? null : `http://${internalHost}:3000`,
I can even reproduce the issue by running Next.js app only in the browser, or running in desktop app by tauri dev. The terminal process will report the compiled status when the file changes have been made, but no hot reload in the browser or in the native desktop simulator.
By comment out the line assetPrefix, hot reload works as expected but it will break the feature the server won't properly resolve your assets..
Hmm, I feel like it'd be better to reach out to the nextjs community instead. As far as we know we simply need this config and I don't think it's our fault if hmr breaks because of it 🤔
We'd appreciate it if you (or anyone reading this) could take on this :)
Describe the bug
Following the Next.js integration Doc, step 3 contains the configuration below. Next.js hot reload feature won't work properly.
I can even reproduce the issue by running Next.js app only in the browser, or running in desktop app by
tauri dev
. The terminal process will report thecompiled
status when the file changes have been made, but no hot reload in the browser or in the native desktop simulator.By comment out the line
assetPrefix
, hot reload works as expected but it will break the featurethe server won't properly resolve your assets.
.Reproduction
Expected behavior
The next.js integration guide, with
assetPrefix
in place, next.js hot reload on code change should work.Full
tauri info
outputStack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: