Now that zapier/zapier uses babel v7, it should be safe to assume we can "raise the tide" and move babel-preset-zapier to v7 as well.
As part of the upgrade I also:
Got rid of the modules option of this preset. This wasn't being used internally so it made sense to simplify the API.
Reverted to always using commonjs for the modules preset-env option, until we figure out how to move to ES modules in zapier/zapier (we need to migrate to a minifier that understands ES6+ code).
Cleaned up the presets used internally.
Added support for flow, dynamic imports, and compiling gql tagged template literals.
Next step would be to try to adopt babel-preset-zapier from zapier/zapier!
Now that
zapier/zapier
uses babel v7, it should be safe to assume we can "raise the tide" and movebabel-preset-zapier
to v7 as well.As part of the upgrade I also:
modules
option of this preset. This wasn't being used internally so it made sense to simplify the API.commonjs
for themodules
preset-env option, until we figure out how to move to ES modules inzapier/zapier
(we need to migrate to a minifier that understands ES6+ code).gql
tagged template literals.Next step would be to try to adopt
babel-preset-zapier
fromzapier/zapier
!