jiti
2.7.0 · 5 May 2026MIT267.2M / weekRepositoryHomepagenpmAtom feed
Upgrading jiti From 1.12.13 to 2.7.0
45 releases in betweennotes for 38
- 1+
- change to make
- 0
- advisories fixed
- 45+
- new
- 53+
- fixes
Counted from 38 of 45 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- Deprecated2.1.0
Release by release
- New
Add explicit resource management (
using/await using) support - New
Support opt-in
tsconfigPaths - New
Support virtual modules
- New
Add
jiti/staticsubpath
- New
- Fixed
interop: Only passthrough default if it is not a promise
- Fixed
- New
Install size reduced from
2.03MBto1.67MB - New
Loading times improved
150ms=>22ms(full transform:180ms=>115ms) - New
Lazy load transformer
- Fixed
cjs-interop: Handle function default exports
- Fixed
Always use native require/import for
node:specifiers
- New
- Fixed
interop: Passthrough module if it is a promise
- Fixed
- New
Use
sha256for cache entries in FIPS mode - New
Support
rebuildFsCache(JITI_REBUILD_FS_CACHE) - Fixed
Interop modules with null/undefined default export
- Fixed
Handle
require(<json>)in register mode
- New
- New
cache: Add
+mapsuffix to fs entries whensourceMapsenabled - Fixed
Use native require cache of loaded entries only for Node.js 22.12.+ compatibility
- New
- Fixed
Interop modules with primitive default export
- Fixed
- New
Support generic type for
jiti.import<T> - Fixed
Try to resolve
.tsfiles with.jsextension from js files
- New
3 other lines we could not sort, mostly version bumps
- 2.1.2
Use local
NodeModuletype - 1.21.5
Update deps
- 1.17.2
Format with prettier
45 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.