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
Building any version of an app with ssr: false in the nuxt.config.ts will fail with a message regarding no such file or directory (looking for server.mjs). The app seems to build fine with SSR: true, but SSR: false will fail with both nuxt generate and nuxt build.
Environment
Darwin
v16.11.1
2.16.0-27226092.034b9901
npm
Webpack
bridge
,ssr
,target
,head
,css
,plugins
,components
,modules
,router
,axios
,pwa
,build
@nuxtjs/emotion@0.1.0
,@nuxtjs/axios@5.13.6
,@nuxtjs/pwa@3.3.5
-
Describe the bug
Building any version of an app with ssr: false in the nuxt.config.ts will fail with a message regarding no such file or directory (looking for server.mjs). The app seems to build fine with SSR: true, but SSR: false will fail with both nuxt generate and nuxt build.
Reproduction
Repository available at: https://github.com/NCLlamas/nuxt-demo-issue
bridge: false
from nuxt.config.tsnpm run generate
to see error in terminal{ "scripts": { "build": "nuxt build", "start": "node .output/server/index.mjs" } }
target: static
from nuxt.config.tsnpm run build
to see error in terminalLogs
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ ✖ Nuxt Fatal Error │ │ │ │ Error: Could not load /Users/llamas/Documents/Development/hi-there/github-issue-reproduce/node_modules/.cache/nuxt/dist/server/server.mjs (imported by │ │ node_modules/@nuxt/nitro/dist/runtime/app/render.mjs): ENOENT: no such file or directory, open │ │ '/Users/llamas/Documents/Development/hi-there/github-issue-reproduce/node_modules/.cache/nuxt/dist/server/server.mjs' │ │ │ ╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
The text was updated successfully, but these errors were encountered: