-
Notifications
You must be signed in to change notification settings - Fork 148
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
modules failing on master with --throw-deprecation #605
Comments
Several of those are modules that I co-maintain. I’ll work on that list. |
I just updated the list. It seems like multiple modules do not show up anymore but we also skipped quite a few of them. We should try to revisit the skipped ones as well and see if we can fix some of those. There are two new deprecation that cause issues: OutgoingMessage.prototype._headers are deprecated and cause deprecation warnings in three modules: It seems like two deprecations do not cause any issues anymore which is nice (maybe more but that requires a closer look at the former entries). Refs: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1842/#showFailuresLink |
If I remember correctly |
I created a project to track them: https://github.com/nodejs/citgm/projects/2
The reason is mainly the deprecation of the Buffer constructor.
Note: currently, npm itself fails to run with
--throw-deprecation
(nodejs/node#23013).You can work around it by replacing
pseudoRandomBytes
manually inlib/node_modules/npm/node_modules/unique-slug/index.js
The text was updated successfully, but these errors were encountered: