-
Notifications
You must be signed in to change notification settings - Fork 197
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
Make import work in node 13 ESM #188
Conversation
After merging this, could you please update the npm package? |
Thank you! |
@mathiasrw : Thank you for merging it so quickly! Thank you also for your thumbs-up on the npm package update. That would be very useful. |
Ill see what I can do. Not sure I have access more. |
I do not remember any of us ever having NPM access. |
Nope - I dont have access any more. I have a feeling that I got that some years ago - but I might be mistaken. Last update was 6 years ago. Time for an npm name change? |
$ npm owner ls paralleljs |
I would prefer not to have to change the NPM name. |
Enlightening (less bureaucratic than I thought!): https://docs.npmjs.com/using-npm/disputes.html |
@benbucksch There is no dispute. The repo is adams, the npm is adams. A dispute would be if we insists that we have the right to the npm name. We dont. We contribute with the rights as the originator see fit. |
Mathias, yes, of course. The title of the document is a bit misleading, but it's also for an unresponsive maintainer. (6 years without releases is something!) Did you contact adams by email? Will he make the release? If yes, no problem, all good. If no, you can make releases again via this process. |
@benbucksch Ok. You are right. I sent him an email cc npm. |
Incredible response time; great support so far 👍🏼 |
Merged and pushed to npm as version 1.0.0 |
That's great! Thank you! |
Fixes issue #187 error: "Cannot find main entry point" in package.json