feat: Optionally hook internal paths like require-in-the-middle#194
Merged
timfish merged 2 commits intonodejs:mainfrom May 24, 2025
Merged
feat: Optionally hook internal paths like require-in-the-middle#194timfish merged 2 commits intonodejs:mainfrom
require-in-the-middle#194timfish merged 2 commits intonodejs:mainfrom
Conversation
jsumners-nr
previously approved these changes
May 23, 2025
AbhiPrasad
reviewed
May 23, 2025
Member
AbhiPrasad
left a comment
There was a problem hiding this comment.
This needs a note in the README
AbhiPrasad
approved these changes
May 24, 2025
Merged
trentm
added a commit
to trentm/import-in-the-middle
that referenced
this pull request
Jan 23, 2026
…dle` (nodejs#194)" This reverts commit 976d032.
BridgeAR
pushed a commit
that referenced
this pull request
Jan 25, 2026
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
3 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.
As discussed in the Diagnostics Working Group meeting, this PR is similar to #189 but allows this change to be selectively enabled so it can be tested more thoroughly before becoming the default.
Sentry are happy to do this testing!