BOM is included in the compiled source.

[petterek]

When using Visual Studio it saves the HTML with BOM as default, this add's the following first line in the

function create_main_fragment ( state, component ) {
	 var text_1_value, text_3_value;
     var text = createText( "´╗┐" ); //this is BOM

The BOM should be ignored

[Conduitry]

I'm not sure whose responsibility this is. The Svelte compiler itself is passed a string, not bytes, and I think it should be able to expect the string to contain just the actual document.

What are you using to actual run Svelte? (Which build tool?) My understanding of how this stuff works is that whichever code is responsible for decoding bytes into strings isn't doing its job correctly.

[petterek]

I am using the cli from PowerShell in Windows

[Conduitry]

Looks like the CLI is always trying to interpret the input as UTF-8. (Aside - I think 'utf8' is what Node calls the encoding, and not 'utf-8'?) Not sure how to best handle this. I'm sure there are established libraries on npm for determining the encoding of a file but I don't have experience with them.

[petterek]

I have actually had the same 'issue' with json files, and "node contex" not able to handle them due to the BOM. Ended up with recoding the files, without BOM.
Unfortunately with BOM is the default in Visual Studio

[dinoboff]

IMO, it's a bug with https://github.com/sveltejs/svelte-cli. Even if it assumes utf8 encoding, it should strip the BOM and maybe add it to the generated components.

See nodejs/node#3040

[nilchaos87]

https://marketplace.visualstudio.com/items?itemName=SergeyVlasov.FixFileEncoding

[Rich-Harris]

Can you try svelte-cli@1.3.7 and see if it fixes this please?

[petterek]

Seems to fix the issue

[petterek]

Great work