Skip to content
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

Open
targos opened this issue Sep 22, 2018 · 3 comments
Open

modules failing on master with --throw-deprecation #605

targos opened this issue Sep 22, 2018 · 3 comments
Labels

Comments

@targos
Copy link
Member

targos commented Sep 22, 2018

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 in lib/node_modules/npm/node_modules/unique-slug/index.js

@mcollina
Copy link
Member

Several of those are modules that I co-maintain. I’ll work on that list.

@BridgeAR
Copy link
Member

BridgeAR commented May 2, 2019

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: fastify, ws and shot (cc @lpinca @mcollina) and TLS Servername to IP causes problems in node-gyp (cc @richardlau @refack).

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

@BridgeAR BridgeAR added meta WIP Work in progress and removed WIP Work in progress labels May 2, 2019
@lpinca
Copy link
Member

lpinca commented May 2, 2019

If I remember correctly outgoingMessage._headers in ws is only used in tests. Should be trivial to fix.
I'll take a look when I can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants