NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #605 most downloaded on npm
Intercept imports in Node.js
Last release 4 days ago
30 Sep 2026
Release timing varies
gaps range from 8 days to 2 months
Nearly every release is documented
notes for 57 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
64 releases · first in 2021
One column per quarter.
remove duplicate TypeScript export names
3.5.0 (2026-09-08) Features support es-module-lexer v3 ( #284 ) ( abdf356 ) Performance Improvements reduce ESM wrapper allocations
allow disabling CJS source stripping
strip TypeScript after loaders normalize format
instrument type-stripped TypeScript modules
add shouldInclude predicate for consumer-owned module matching
add synchronous loader hooks via module.registerHooks
Updated proxying logic for builtins that are used as CJS
handle file specifiers from turbopacked packages better
## 3.0.0 (2026-01-30) ### ⚠ BREAKING CHANGES * drop support for Node.js < v18
ensure the callback 'name' arg is the module name when matching the module main file, even when 'internals: true' option is used
do not instrument the top level module
add missing JSDoc type information
properly hook submodule package exports
The hook code has been converted to ESM to work around some loader issues. There should actually be no breaking changes when using import-in-the-middl…
This was only a new major out of an abundance of caution. The hook code has been converted to ESM to work around some loader issues. There should actually be no breaking changes when using import-in-the-middle/hook.mjs or the exported Hook API.
Converting all modules running in the loader thread to ESM should not be a
breaking change for most users since it primarily affects internal implementation
details. However, if you were referencing internal CJS files like hook.js this will no longer work.
Compatibility with specifier imports
Revert "use createRequire to load hook.js (#205)"
use createRequire to load hook.js
do not replace dollar sign in shim variable name
Account for invalid identifiers
Optionally hook internal paths like require-in-the-middle
Don't attempt to wrap TypeScript modules
## 1.13.0 (2025-02-06) ### Features * Support import attributes
Correct type definition for waitForAllMessagesAcknowledged
do nothing if target does not exist in getters map
## 1.11.1 (2024-09-26) ### Bug Fixes * Support Hooking multiple times
Allow passing of include or exclude list via module.register()
fix: Named export Hook missing from types by @timfish in https://github.com/DataDog/import-in-the-middle/pull/92
Hook missing from types by @timfish in https://github.com/DataDog/import-in-the-middle/pull/92parentResolve is not a function by @timfish in https://github.com/DataDog/import-in-the-middle/pull/100export * by @timfish in https://github.com/DataDog/import-in-the-middle/pull/103parentLoad if parsing fails by @timfish in https://github.com/DataDog/import-in-the-middle/pull/104Full Changelog: https://github.com/DataDog/import-in-the-middle/compare/v1.8.0...v1.8.1
test: skip static-import on > v21 by @timfish in https://github.com/DataDog/import-in-the-middle/pull/81
Hook named export by @timfish in https://github.com/DataDog/import-in-the-middle/pull/88Full Changelog: https://github.com/DataDog/import-in-the-middle/compare/v1.7.4...v1.8.0
Nothing published for this version
Fix duplicate default exports #53
Nothing published for this version
Revert "Fix loader cyclical dependency bug (https://github.com/DataDog/import-in-the-middle/pull/36)"
Fix loader cyclical dependency bug for Node.js >= v16.0.0
Add extensionless support in 18.19
Nothing published for this version
sanitizes URLs passed to import, fixing a security vulnerability: CVE-2023-38704
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
> This version of the library contains a known security vulnerability: CVE-2023-38704.
Warning This version of the library contains a known security vulnerability: CVE-2023-38704. We recommend upgrading immediately to at least v1.4.2.
Your coding agent can read these notes before it upgrades. Set up the MCP server →