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
{{ message }}
This repository was archived by the owner on Jan 11, 2023. It is now read-only.
Regarding this feature, I would expect the output .html file to end up in the static folder to be pushed to the CDN with all other assets, though this makes subsequent builds messy as they would have to cleanup the generated files in static. Perhaps tracking them in the __sapper__/build/build.json manifest we would be able to cleanup the prior output files before generating the new build and manifest.
It'd be great if we had the same kind of build time static optimization that nextjs has https://nextjs.org/docs/advanced-features/automatic-static-optimization
We could probably just see if a page has a
preload
at build time and, if not, "export" that component tostatic
or something like that.Besides the performance gain, if someone was making a static site with sapper it would automatically
export
it tostatic
which is kind of neat.The text was updated successfully, but these errors were encountered: