-
Notifications
You must be signed in to change notification settings - Fork 150
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
npm #1
Comments
Dupe of #8 |
You might want to hold off on the exports and go straight to ES modules, which will be standard across all JS VMs. This will be much better than using Node's CommonJS because it will not require an extra build step for browser versus Node, and since you've already been waiting a while to do it right, why not wait to really do it right with ES Modules? Those are my thoughts. |
Thanks for the info. Admittedly I'm not a JS guy and it's hard to stay on top of all of this. I do have an exports patch that's 95% done, just need to find the motivation for the last push |
@brian-armstrong, is there any update on your progress? |
I've put the first bit of my work for this here #24 |
In case there are still people interested, I made this module for a personal project. It is quite dirty but it works (web only) and will probably the job until quiet-js is officially published to npm. Feel free to fork it or send PRs if you have improvements to suggest. |
This package should make its way onto npm. In order to get there, I'd like to do a bit of cleanup and make a proper
exports
.The text was updated successfully, but these errors were encountered: