-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
ES modules #1380
Comments
Pull requests are welcome. If you can get rid of the requires and support ES modules I wouldn't see why that wouldn't be a good thing. Currently it's not really on any of our radars. Could you maybe explain what the use case is a little bit more? Thanks. |
Asking a friend, he recommended we wait for NodeJS to support ES modules. Since a lot of our dependencies are NodeJS and don't have typescript support, it is difficult at this time. |
Sounds reasonable, thanks!
…On Tue, Apr 9, 2019, 3:24 AM Jonathan Underwood ***@***.***> wrote:
Asking a friend, he recommended we wait for NodeJS to support ES modules.
Since a lot of our dependencies are NodeJS and don't have typescript
support, it is difficult at this time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1380 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGrSjyxpQM_hggHXXfjddIjZzOZE-zQGks5vfFxBgaJpZM4cjmCG>
.
|
This allows the npm package to add a new directory next to The existing |
This should be revisited since ES Modules have had time to cook and get more adoption. Thoughts on whether a full ESM library would be better than some sort of hybrid thing? I publish hybrid packages for tiny-secp256k1 and uint8array-tools... but a lot of bundlers still have trouble with them apparently. |
It would be great if the library could support ES modules. It would be nice to use an ES module build directly in the browser without a bundler, or use the TypeScript code directly. The use of requires in the source code precludes this
The text was updated successfully, but these errors were encountered: