Node 16.x breakpoint warning resolved in 16.4#1044
Merged
connor4312 merged 1 commit intomicrosoft:mainfrom Jun 27, 2021
Ashesh3:patch-1
Merged
Node 16.x breakpoint warning resolved in 16.4#1044connor4312 merged 1 commit intomicrosoft:mainfrom Ashesh3:patch-1
connor4312 merged 1 commit intomicrosoft:mainfrom
Ashesh3:patch-1
Conversation
Since the said issue is resolved and shipped in 16.4, Suggesting users to downgrade is a bad idea, instead they should be recommended to upgrade to the latest release to resolve this issue. Reference: nodejs/node#38273
connor4312
approved these changes
Jun 27, 2021
Member
|
Excellent, thanks! I think, in the future for these cases, we should say to try upgrading if a newer version is available. |
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
2 participants
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.
Since the said issue is resolved and shipped in 16.4, Suggesting users to downgrade is a bad idea, instead they should be recommended to upgrade to the latest release to resolve this issue.
Reference: nodejs/node#38273