You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2022. It is now read-only.
I expect to be able to consume an ES6 project if my toolchain supports it, but I don't want to run babel on all of YoastSEO.js.
What happened instead?
I have to run babel on all of YoastSEO.js or I can't use ES6 modules.
Technical details
For an example of how this could work you could look at Gutenberg. They build to a build folder and a build-module folder. build is then specified as the main entry point in the package.json. build-module is specified as module entry point in the package.json. In both builds all other ES6 syntax is transpired down to ES5.
The text was updated successfully, but these errors were encountered:
What did you expect to happen?
I expect to be able to consume an ES6 project if my toolchain supports it, but I don't want to run babel on all of YoastSEO.js.
What happened instead?
I have to run babel on all of YoastSEO.js or I can't use ES6 modules.
Technical details
For an example of how this could work you could look at Gutenberg. They build to a
build
folder and abuild-module
folder.build
is then specified as themain
entry point in thepackage.json
.build-module
is specified asmodule
entry point in thepackage.json
. In both builds all other ES6 syntax is transpired down to ES5.The text was updated successfully, but these errors were encountered: