Replace webpack with Parcel

[fregante]

Closes #34

Based on fregante/GhostText#187, npmhub/npmhub#119, tanmayrajani/notifications-preview-github#113

But this PR introduces some cool changes like the preservation of webextension-polyfill without any bundling whatsoever, so it can be imported globally and once instead of once per bundle.

Wishlist/todo

• Flat output How can I get all the output files in a single, flat directory? parcel-bundler/parcel#5858
• Update docs
• Ensure it actually works
• Somehow extract webext-options-sync to its own "vendor" entry so it's not bundled 3 times separately [Web Extension Transformer] doesn't support code splitting parcel-bundler/parcel#5859
• Do not minify manifest.json WebExtensionTransformer: Beautify manifest.json parcel-bundler/parcel#5860
• Restore partial minification like webpack had

Current output

❯ nr build
✨ Built in 2.39s

distribution/manifest.json                                                        565 B     92ms
distribution/icon.png                                                           1.14 KB     75ms
distribution/__/node_modules/webextension-polyfill/dist/browser-polyfill.js    36.61 KB    196ms
distribution/background.js                                                     33.61 KB    199ms
distribution/options.html                                                       1.05 KB    686ms
distribution/options.ed4d9118.css                                                 906 B    688ms
distribution/options.a7e143c4.js                                               34.95 KB    689ms

[fregante]

Another Parcel issue I found is that --no-content-hash doesn't seem to work because options.[hash].js changes hash depending on content.

This isn't an immediate issue here but it's an issue for Safari extensions because (sigh) Xcode configuration files include a static list of files to include.

[mischnic]

Yeah, I've noticed that as well: parcel-bundler/parcel#5894

[fregante]

Thank you, excellent!

[fregante]

Since parcel-bundler/parcel#5858 isn't currently possible, I temporarily avoided that issue altogether with the commit above. This requires the user to manually load the polyfill in every file in order to use the browser API, but at least people can already start using Parcel without us having to wait for a fix.