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
Allow es-check to check individual modules located in node_modules folder with their nested dependencies in a similar way like are-you-es5 do it.
Scenario:
I have a frontend react project with dependencies in package.json
One of those dependencies package-example-in-es2022 includes es2022 code i.e. nullish coalescing
When I run webpack build, es2022 code in my project gets transpiled by babel, but dependencies from node_modules are not (unless specified in the config), so package-example-in-es2022 with nullish coalescing will cause an issue in browsers like < Chrome 80, < Firefox 72, < Opera 67, < Safari 13.1
In result I'll end up with build unable to run in browsers with lower versions than specified above
With this feature I would like to be able to identify non-es5 dependencies and list them in a way so they can be easily imported in babel config, so babel will transpile them. I think listing package names is good enough, it can be used then to generate regex easily.
Why Is This Update Needed?
To automate node builds.
If I run es-check in my project, with is a module with "package.json", I would expect to execute es-check for each dependency (and their nested dependencies), and list incompatible modules.
Are There Examples Of This Requested Update Elsewhere?
are-you-es5 unfortunately packages can't detect es2022, probably due to no updates since 2 years
The text was updated successfully, but these errors were encountered:
Requested Update
Allow es-check to check individual modules located in
node_modules
folder with their nested dependencies in a similar way like are-you-es5 do it.Scenario:
package.json
package-example-in-es2022
includes es2022 code i.e. nullish coalescingnode_modules
are not (unless specified in the config), sopackage-example-in-es2022
with nullish coalescing will cause an issue in browsers like < Chrome 80, < Firefox 72, < Opera 67, < Safari 13.1With this feature I would like to be able to identify non-es5 dependencies and list them in a way so they can be easily imported in babel config, so babel will transpile them. I think listing package names is good enough, it can be used then to generate regex easily.
Why Is This Update Needed?
To automate node builds.
If I run es-check in my project, with is a module with "package.json", I would expect to execute es-check for each dependency (and their nested dependencies), and list incompatible modules.
Are There Examples Of This Requested Update Elsewhere?
are-you-es5 unfortunately packages can't detect es2022, probably due to no updates since 2 years
The text was updated successfully, but these errors were encountered: