Open SterlingKelley opened 1 year ago
Is it possible to upgrade the version of the tracer you're using?
I believe the commit you've linked to from a year ago only affects the end of life v2.x branch, but never landed in the currently maintained v3.x and v4.x branches.
If not, you could probably fork this repo, checkout the v2.x branch, make a commit to revert the 7fbc0c4807e00f6e246bc37437ecc3a54c0b2a19 commit, push it to your fork, then point to that in your package.json file. Here's some more information:
https://docs.npmjs.com/cli/v9/configuring-npm/package-json?v=true#git-urls-as-dependencies
Expected behaviour
@hapi/hapi
should be instrumentedActual behaviour Only
@hapi/hapi <=20.2.1
is instrumentedSteps to reproduce
Environment
Support for newer versions of
@hapi/hapi
was explicitly dropped in this commit likely due to Hapi 21 dropping support for older version of Node. However the latest version of Hapi 20 is not instrumented as a result.