html in ssr components are not minified

[hgl]

Describe the bug

1. run npm run build
2. open __sapper__/build/server/server.js
3. search for create_ssr_component(($$result
4. look at the unminifed html string

Information about your Sapper Installation:

• Sapper version (Please check you can reproduce the issue with the latest release!)
  0.27.9
• Svelte version (Please check you can reproduce the issue with the latest release!)
  3.12.1

Additional context
I was looking at the source code of returned html in browser (npm run start, not dev version), and found the html were mostly unminified.

Jup, just came here after encountering the same unwished behaviour. I hope this can get addressed soon...

[jeromebon]

I don't think it's svelte issue. You can add an express midleware to minfy your html. Or if you use export there is external tools to do so.
Is there any case where it's not enought?

@Mojeer0 Adding express middleware means that Express has to modify the source in memory, the source itself will not be changed from what I've heard. I know the few newlines aren't a huge drama, but I'm a perfectionist and it just seems off when I've minified everything else over rollup, but the production output of sapper contains unminified html. I'd appreciate some official guidance on how to achieve this.

[szkosma]

+1

[benmccann]

There's actually a helper method to minify html already:

sapper/src/api/utils/minify_html.ts

Line 3 in f3e9fc4

export default function minify_html(html: string) {

[szkosma]

There's actually a helper method to minify html already:

sapper/src/api/utils/minify_html.ts

Line 3 in f3e9fc4

export default function minify_html(html: string) {

This appears to be used to minify the template.html file on build... I don't see any obvious way to use it to minify SSR output, unless I'm mistaken?

[benmccann]

I'm not saying there's an easy way to use that method as an end user today, but that an implementation of this feature could utilize that method

We might want to open an issue at svelte-preprocess instead. It can already transform svelte component html (it supports pug for example), so we could ask the maintainer to maybe add an option to minify it as well.