Multi-line comments breaking chrome unpacked extension loading

[melink14]

Reported here #363 (reply in thread) and confirmed by me recently.

Uncaught SyntaxError: Invalid or unexpected token

var __webpack_exports__ = {};
/*

data.js:2 (無名関数)

[melink14]

Probably caused by a BOM character being before the start of the file but after the webpack_exports.

But Sam said removing multiline comments fixed it for him...

[melink14]

It looks like I can fix it by adding <meta charset="utf-8" /> to my background.html which I guess lets chrome know to expect those non breaking space characters.

[melink14]

It seems that it's also caused by the ts files being saved as UTF-8 with BOM in vscode which gets treated weirdly after compilation.

For some reason only data.ts and rikaichan.ts have this encoding so only they cause the problem.

Probably better to just resave the files without the encoding but I wonder if that will show up in version control

[melink14]

There's a eslint rule for encoding which I'll turn on to ensure no BOM problems.

Editor config has it but vscode doesn't support it yet.

If we wanted bom files then the html meta tag solution or a webpack plugin to add BOM would work.

[melink14]

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

• Chrome Web Store
• GitHub release

Your semantic-release bot 📦🚀