chore: fix deprecation warning with Node.js 16 imports#6248
Closed
mxschmitt wants to merge 1 commit into
Closed
Conversation
mxschmitt
changed the title
mxschmitt
force-pushed
the
bugfix/node-16-deprecation-warning
branch
from
3b33a2a to
00ac4ff
Compare
Contributor
Author
|
Closing for now, nobody reported any issues. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This isn't a quick-one, with a change we probably break previous Node.js versions. For reference
Fixes #6026
See here #6026 (comment) for reproducible steps.