fix: Updated instrumentation registration to allow for instrumenting of a local file that does not exist within node_modules. You must pass in absolutePath
with the absolute path to the file that is being instrumented along with the moduleName which in this case is just the file name without the extension
#1974
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.
Description
We tried to add instrumentation for local files. This was done in [messaging-app] but was using v9.x of the agent. In v11.0.0 we now use
require-in-the-middle
for instrumenting CJS, which requires additional work to instrument files that are not within a 3rd party module. This PR fixes that by providing a newabsolutePath
key:How to Test
node test/integration/module-loading/module-loading.tap.js
adds a new test for this.Related Issues
Closes #1973