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
Is your enhancement related to a problem? Please describe.
The Node.js ecosystem is evolving and there's a push for shipping ESM-only packages.
Given we're already supporting only Node.js >= 16 it should be relatively safe to switch 10up-toolkit from commonjs to ESM Modules in the next major version.
There are several deps we're relying on where new versions only ships ESM and therefore we cannot update them yet.
Since this is mostly a CLI tool it won't force users to switch their projects to ESM. Additionally, we can still export the configs files via commonjs so that users can extend the config as usual without having to switch to ESM modules.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is your enhancement related to a problem? Please describe.
The Node.js ecosystem is evolving and there's a push for shipping ESM-only packages.
Given we're already supporting only Node.js >= 16 it should be relatively safe to switch 10up-toolkit from commonjs to ESM Modules in the next major version.
There are several deps we're relying on where new versions only ships ESM and therefore we cannot update them yet.
Since this is mostly a CLI tool it won't force users to switch their projects to ESM. Additionally, we can still export the configs files via commonjs so that users can extend the config as usual without having to switch to ESM modules.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: