Package Exports
- import-in-the-middle
- import-in-the-middle/hook.mjs
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (import-in-the-middle) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
import-in-the-middle
import-in-the-middle is an module loading interceptor inspired by
require-in-the-middle, but
specifically for ESM modules. In fact, it can even modify modules after loading
time.
Usage
The API for
require-in-the-middle is followed as closely as possible as the default
export. There are lower-level addHook and removeHook exports available which
don't do any filtering of modules, and present the full file URL as a parameter
to the hook. See the Typescript definition file for detailed API docs.
You can modify anything exported from any given ESM or CJS module that's imported in ESM files, regardless of whether they're imported statically or dynamically.
import Hook from 'import-in-the-middle'
import { foo } from 'package-i-want-to-modify'
console.log(foo) // whatever that module exported
Hook(['package-i-want-to-modify'], (exported, name, baseDir) => {
  // `exported` is effectively `import * as exported from ${url}`
  exported.foo += 1
})
console.log(foo) // 1 more than whatever that module exportedThis requires the use of an ESM loader hook, which can be added with the following command-line option.
--loader=import-in-the-middle/hook.mjsLimitations
- You cannot add new exports to a module. You can only modify existing ones.
- While bindings to module exports end up being "re-bound" when modified in a hook, dynamically imported modules cannot be altered after they're loaded.
- Modules loaded via requireare not affected at all.