Skip to content

Conversation

@guybedford
Copy link
Contributor

This fixes an issue with the deprecation warning introduced in #35747 which was triggering incorrectly for third-party package resolutions in Windows.

Should have tested the negative case fully, but at least it has made people aware of the deprecation who have been using Node.js 15.

An alternative might be to just go ahead and apply this warning for all resolutions anyway, but let's stick to the plan of a slow deprecation for now at least.

@nodejs/modules

@aduh95aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Jan 10, 2021
@github-actionsgithub-actionsbot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jan 10, 2021
@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

PR-URL: nodejs#36859 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Geoffrey Booth <[email protected]> Reviewed-By: Myles Borins <[email protected]>
@aduh95aduh95force-pushed the subpath-deprecation-win-fix branch from 6daadf1 to 2e909c4CompareJanuary 12, 2021 13:46
@aduh95
Copy link
Contributor

Landed in 2e909c4

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@guybedford@nodejs-github-bot@aduh95@jasnell@GeoffreyBooth@MylesBorins@targos