-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support reporting libraries that have the module entrypoint #45
Comments
Hey @roopakv, I'm really sorry for the late reply, I think something ate the notification on my side. We're completely relying on My Node.js/JavaScript usage has gone down a lot since I first wrote this library actually, so please forgive me if I've said anything that doesn't make any sense. EDIT
|
@roopakv since it seems that bundlers always prefer to use the module entry point, what do you think of simply counting those packages as ES6 then? That should make them show up in the regex for transpilation. My only concern is if there are bundlers that let you pick between main/module entry points somehow, is that something we have to worry about or are they always picking the module version? |
@obahareth so webpaack allows you to pick which entry point to use. However as a start using module followed by main seems like a great start to me. wdyt? |
While the presence of the module entrypoint automatically suggests the libraries don't have es5, it is helpful because of the following case:
We polyfill using core-js and the "usage" mechanism. If a module has the
module
entrypoint we need it to be transpiled so that it is polyfilled.if
are-you-es5
had an option to return libraries that have a module entrypoint we could use that to decide if they would be transpiled.The text was updated successfully, but these errors were encountered: