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
Fix audited packages, support Node 10, drop support for Node 4 #73
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This implies that the library can no longer be bundled for the browser without compilation. Is that worth bumping the major..? Not sure if anybody is depending on this.
BREAKING CHANGE: This removes support for Node 4 as well as for bundling the library for the browser without compilation.
846d5ee
to
16800e3
Compare
Agreed @jkrems 👍 commit message updated. |
@@ -17,6 +17,10 @@ | |||
"test": "mocha", | |||
"posttest": "nlm verify" | |||
}, | |||
"engines": { | |||
"yarn": "0.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yarn unfortunately has some very unique ideas about how to interpret the engines field. We use it here to clearly mark this project as using package-lock. If you're using it in your project with yarn, I'd suggest adding something like this to your .npmrc
(project-level):
ignore-engines=true
I hope that helps unblock you but we'll also look into ways to still mark this library as non-yarn-using while supporting people that use yarn's default engines handling.
No description provided.