-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing .output/public/index.html after upgrading to RC12 #15340
Comments
Are you running Related: nuxt/framework#7831. |
@danielroe thanks for your response. Yes I was running |
I'm having the same issue, using "npm run build" with "ssr: false" is not generating any html files but "npm run generate" with "ssr: false" is prerendering all the routes. |
This is intended behaviour (not generating the index when running To generate only one route you can do: export default defineNuxtConfig({
nitro: {
prerender: {
crawlLinks: false,
routes: ['/']
}
}
}) |
Environment
Linux
v16.18.0
3.0.0-rc.12
0.6.0
npm@8.19.2
vite
ssr
,modules
,buildModules
,build
,css
,head
,pwa
,runtimeConfig
@nuxtjs/tailwindcss@5.3.5
,@vueuse/nuxt@9.4.0
,@kevinmarrec/nuxt-pwa@0.8.0
@pinia/nuxt@0.4.3
Reproduction
Currently I am building my nuxt3 application without SSR (via setting
ssr: false
innuxt.config.ts
).Up until the upgrade from nuxt3 RC11 to RC12 there was an index.html file located in .output/public after building the application using
nuxt build
and I was able to deploy the generated SPA Application via AWS Amplify as example using the following config:Describe the bug
after building locally i noticed that the file .output/public/index.html was missing after upgrading from RC11 to RC12. Now with the index.html file missing, Its is not possible anymore to host a SPA without prerendered routes.
Please correct me if I missunderstood something there ✌️.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: