Fix build for Gatsby (WebPack v1). #1107
Conversation
WebPack version 1, which Gatsby is using, has the Acorn parser set to parse ES6 and lower. The latest version of WebPack supports parsing up to ES2017 and lower (webpack/lib/Parser.js), but Gatsby isn't using it.
|
Deploy preview for netlify-cms-www ready! Built with commit 8d74a32 |
|
Deploy preview for cms-demo ready! Built with commit 8d74a32 |
|
We should be able to just add our own babel loader for the cms script to Gatsby's webpack. Giving that a shot now, I'll link the PR if it works. |
|
For posterity, the latest thought is that babel-preset-env may not be such a great fit for distributed packages, where transpilation considerations are less about the end product and more about the tooling of consumers. It makes sense at the moment to be presciptive about what exactly we're transpiling, which doesn't map to a specific browsers support model. Merging this PR is the first step, but we may go ahead and remove babel-preset-env entirely in the future, instead using exactly what we need for the desired output. |
WebPack version 1, which Gatsby is using, has the Acorn parser set to
parse ES6 and lower. The latest version of WebPack supports parsing up
to ES2017 and lower (webpack/lib/Parser.js), but Gatsby isn't using it.
This isn't something we want to do permanently, as packages should be able to do this themselves. We do have a lot of Gatsby users, though, so this is a temporary fix for now.
Closes #1097.