chore(deps): update import-in-the-middle to 3.5.1

[BridgeAR]

import-in-the-middle 3.5.1 uses optimized ModuleBinder registration for regular ESM instrumentation. The release restores the pre-3.5 interfaces used by existing bundler integrations, so no bundler migration is required.

[dd-octo-sts]

Overall package size

Self size: 8.91 MB
Deduped: 9.65 MB
No deduping: 9.65 MB

Dependency sizes

| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.5.1 | 127.66 kB | 513.61 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |

_{🤖 This report was automatically generated by heaviest-objects-in-the-universe}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.70%. Comparing base (1a27b21) to head (086ccb9).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #10304   +/-   ##
=======================================
  Coverage   98.70%   98.70%           
=======================================
  Files        1012     1012           
  Lines      159392   159392           
  Branches       74       74           
=======================================
  Hits       157326   157326           
  Misses       2066     2066           

Flag	Coverage Δ
ai-guard	65.19% <ø> (-0.02%)	⬇️
apm-capabilities	63.70% <ø> (ø)
apm-integrations	81.45% <ø> (-0.02%)	⬇️
appsec	58.91% <ø> (-0.01%)	⬇️
debugger	69.80% <ø> (-0.06%)	⬇️
instrumentation	54.30% <ø> (-0.01%)	⬇️
llmobs	79.07% <ø> (-0.02%)	⬇️
master-coverage	98.70% <ø> (?)
openfeature	66.38% <ø> (-0.03%)	⬇️
platform	69.30% <ø> (-0.01%)	⬇️
profiling	66.73% <ø> (-0.03%)	⬇️
serverless	65.72% <ø> (-0.02%)	⬇️
test-optimization	82.57% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[datadog-datadog-us1-prod]

⚠️ Warnings

⚠️ Your PR has warnings. Tests failed — unable to determine if these are from required jobs.

🧪 1 Test failed in 1 job

AppSec | integration — ❌ 1 test failed

View more details · View in GitHub Actions

❌ esbuild support for IAST cjs "before all" hook in "cjs" from cjs  

Command failed: npm install

Error: Command failed: npm install

    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at ChildProcess.exithandler (node:child_process:422:12)
    at ChildProcess.emit (node:events:524:28)
    at maybeClose (node:internal/child_process:1104:16)
    at ChildProcess._handle.onexit (node:internal/child_process:304:5)
...

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 98.18% (+0.00%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 086ccb9 | Docs | View more details | Give us feedback!}

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-11 19:42:38

Comparing candidate commit 086ccb9 in PR branch BridgeAR/2026-09-11-iitm-3-5-1 with baseline commit 1a27b21 in branch master.

📊 Benchmarking dashboard

Found 1 performance improvements and 0 performance regressions! Performance is the same for 2302 metrics, 10 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:startup-with-tracer-everything-esm-24

• 🟩 max_rss_usage [-8.503MB; -4.836MB] or [-4.014%; -2.283%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:appsec-appsec-enabled-24

• unstable max_rss_usage [-26.140MB; +8.379MB] or [-9.156%; +2.935%]

scenario:appsec-iast-with-vulnerability-iast-enabled-default-config-20

• unstable max_rss_usage [-21.401MB; +13.809MB] or [-6.205%; +4.004%]

scenario:debugger-line-probe-with-snapshot-minimal-26

• unstable max_rss_usage [-10.492MB; +14.462MB] or [-4.268%; +5.883%]

scenario:debugger-line-probe-without-snapshot-26

• unstable max_rss_usage [-9.620MB; +18.105MB] or [-3.895%; +7.331%]

scenario:encoders-0.4-immediate-flush-20

• unstable max_rss_usage [-7.277MB; +9.861MB] or [-9.347%; +12.668%]

scenario:llmobs-encode-unicode-mixed-20

• unstable max_rss_usage [-10.873MB; +7.739MB] or [-14.524%; +10.338%]

scenario:plugin-cassandra-driver-batch-24

• unstable execution_time [-101.220ms; +138.687ms] or [-4.614%; +6.321%]

scenario:plugin-graphql-long-with-depth-off-26

• unstable max_rss_usage [-33.161MB; +17.542MB] or [-15.930%; +8.427%]

scenario:plugin-graphql-long-with-depth-on-max-26

• unstable max_rss_usage [-45.206MB; +20.822MB] or [-19.285%; +8.882%]

scenario:plugin-pg-service-26

• unstable execution_time [-79.152ms; +111.751ms] or [-4.845%; +6.840%]