Babel version & config and other updates

[anderly]

Babel version & config and other updates

[anderly]

Cool, thanks. Yes, I noticed they validate on their end and reject if invalid, so I had removed the esprima package as well.

I'm already using this boilerplate as a very lightweight edge oauth proxy which is working nicely and I don't have to worry about being the central bottleneck standing up my own oauth proxy server(s).

[anderly]

Thanks Dave!

If this is simply running in a CloudFlare worker and not in a browser, I don't think I even need babel@polyfill or maybe even babel@preset-env. Thoughts?

Thanks for the heads up on deploy and the link to your updates.

[detroitenglish]

Dug into a bit and learned that Cloudflare always keeps the worker runtime in line with the latest Chrome version. So now babel-polyfill indeed seems unnecessary.

I'm definitely keeping babel@preset-env though; with Babel 7 it's so much nicer to use e.g. import and object-rest-spread and never worry about installing plugins or tooling.

[anderly]

10-4. On that link it says "This means you can safely use latest JavaScript features, with no need for “transpilers”. So, I wonder if we really need babel at all? Will import not work without it. rest and spread operators appear to work without needing babel. However, I did see your use of the closure elimination plugin which is nice. For now, I've synced it up with your changes but I'm gonna try removing babel completely and see what, if anything, breaks.

[detroitenglish]

Transpilation of the worker script might not be necessary, but I for one 'never leave home' without Babel. Mostly just to save me from myself; I can't be bothered to keep up with browser compatibilty and what APIs need polyfilling where. Also my IDE would go bananas. Curious if/how Husky precommit linting will work without Babel installed...

Another thing I learned that doesn't seem to be documented: Cloudflare actually validates uploaded worker scripts on their end, and will reject invalid scripts with a 400 response. So esprima validation isn't necessary in the deployment script.

Pushed some minor updates removing esprima and tweaking some tooling config, nothing drastic.