Sapper Export does not render many nested closing tags #1702
Comments
I have to update this issue. The real issue seems to be like sapper is not closing TONS of tags. If you look at the output, lots and lots are missing closing tags. This is a bit bigger issue than I first posted, but hopefully not too bad to patch :). |
It shouldn't break anything and results in smaller download size. I believe SvelteKit does not have this if you'd simply like to wait until then |
Interesting. I think it may be breaking my integration with netlify forms post-processing of the HTML, but not sure. Thanks for letting me know. Is there any way to disable this for now? |
Here's the link if anyone is trying to follow this later https://community.netlify.com/t/netlify-forms-detected-but-not-being-properly-hydrated-in-ci-cd-and-not-submitting-svelte-sapper/30893/2 |
Sapper Export
Sapper export does not render markup after the %sapper.html% tag
To Reproduce
Create a new app with the template project.
Now, open up the
__sapper__/export
folder and view theindex.html
. Scroll to the end of the file, and notice there is no closing tag or anything else that comes after %sapper.html%. You can run a code formatter to see this easier.Expected behavior
Sapper should render html after the %sapper.html% tag
Information about your Sapper Installation:
npx envinfo --system --npmPackages svelte,sapper,rollup,webpack --binaries --browsers
Severity
This is an annoyance that might be breaking my integration with netlify forms, but who really knows?
The text was updated successfully, but these errors were encountered: