We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since 1.0.0-next.587, PR 8131 it seems that using prerender = 'auto' is broken and doesn't pre-render any files.
prerender = 'auto'
Stackblitz reproduction
npm run build and then inspect the build folder (there is no prerendered subfolder). Dropping back down to 1.0.0-next.586 works as expected.
npm run build
build
prerendered
1.0.0-next.586
No response
System: OS: Linux 5.0 undefined CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz Memory: 0 Bytes / 0 Bytes Shell: 1.0 - /bin/jsh Binaries: Node: 16.14.2 - /usr/local/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 7.17.0 - /usr/local/bin/npm npmPackages: @sveltejs/adapter-node: ^1.0.0 => 1.0.0 @sveltejs/kit: 1.0.0-next.587 => 1.0.0-next.587 svelte: ^3.54.0 => 3.55.0 vite: ^4.0.0 => 4.0.3
annoyance
The text was updated successfully, but these errors were encountered:
fix: prerender page when prerender set to 'auto' and ssr set to true
97deab0
fixes #8263
fix: prerender page when prerender set to 'auto' and ssr set to true (#…
130abe4
…8481) fixes #8263
Successfully merging a pull request may close this issue.
Describe the bug
Since 1.0.0-next.587, PR 8131 it seems that using
prerender = 'auto'
is broken and doesn't pre-render any files.Reproduction
Stackblitz reproduction
npm run build
and then inspect thebuild
folder (there is noprerendered
subfolder).Dropping back down to
1.0.0-next.586
works as expected.Logs
No response
System Info
Severity
annoyance
Additional Information
No response
The text was updated successfully, but these errors were encountered: