Issues

`jiti/register`: TypeScript modules loaded by Node only export `default`, and an entry in an import cycle runs twice

unjs/jiti#502 · opened

on Nov 8, 2026

`jiti/register`: `import.meta.resolve()` throws `ReferenceError: jitiESMResolve is not defined`

unjs/jiti#501 · opened

on Nov 7, 2026

`jiti <script>`: `require.main === module` and `import.meta.main` are false for the entry script

unjs/jiti#500 · opened

on Nov 7, 2026

Bare `import.meta` is not transformed, so helpers receive the wrapper's meta (a data: URL) and native resolve

unjs/jiti#497 · opened

on Nov 5, 2026

normalizeParentURL guard tests the undefined identifier `filename`, so plain paths are never converted to file URLs

unjs/jiti#495 · opened

on Nov 5, 2026

jiti's `import.meta.resolve` throws for nonexistent targets; Node and Bun do not

unjs/jiti#494 · opened

on Nov 5, 2026

`jiti/native` passes a parent URL that Node only honors behind a flag

unjs/jiti#493 · opened

on Nov 5, 2026

Concurrent `jiti.import()` calls evaluate a shared dependency twice

unjs/jiti#490 · opened

on Nov 5, 2026

`module.children` misses cached and native dependencies

unjs/jiti#489 · opened

on Nov 5, 2026

Module that fails during sync `require()` stays in the runtime cache with partial exports

unjs/jiti#487 · opened

on Nov 5, 2026

Concurrent import() of a module that is still evaluating returns its partially evaluated exports

unjs/jiti#484 · opened

on Nov 4, 2026

Import attributes (`with { type }`) are silently dropped in transformed modules

unjs/jiti#483 · opened

on Nov 4, 2026

DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.

unjs/jiti#480 · opened

on Oct 26, 2026

1

fs cache: a concurrent store can be read as a hit with NUL bytes (non-atomic writeFileSync)

unjs/jiti#477 · opened

on Oct 20, 2026

interopDefault cache throws TypeError (Proxy invariant) after Object.defineProperty on an export

unjs/jiti#475 · opened

on Oct 13, 2026

Slow resolution of `./foo.js` imports that point at `./foo.ts`

unjs/jiti#472 · opened

on Oct 6, 2026

CJS module returns with two nested layers of `default`

unjs/jiti#468 · opened

on Sep 17, 2026

Feedback from pi extension loader: lazy transform, bare aliases, native passthrough, cache invalidation

unjs/jiti#467 · opened

on Sep 16, 2026

fsCache default: node_modules/.cache/jiti never resolves for file-path instance ids (silent TMP_DIR fallback)

unjs/jiti#459 · opened

on Aug 13, 2026

`interopDefault`'s caching Proxy (#421) breaks ESM live bindings for mutable exports

unjs/jiti#457 · opened

on Aug 12, 2026

[Bug]: jiti config import resolver in rspack fails to respect --perserve-symlinks / jiti gives no symlink-following customization options to fix this

unjs/jiti#445 · opened

on May 20, 2026

Pass `filename` to the Babel transform

unjs/jiti#442 · opened

on May 19, 2026

2

tsconfigPaths behaves not the same as tsc

unjs/jiti#440 · opened

on May 11, 2026

2

Bug: `interopDefault` proxy returns bound functions, breaking native `await using` (Node 24+)

unjs/jiti#437 · opened

on May 5, 2026

Give an error when a default import failed

unjs/jiti#434 · opened

on Apr 9, 2026

Navigation Menu

Repository navigation

Issues

`jiti/register`: TypeScript modules loaded by Node only export `default`, and an entry in an import cycle runs twice

`jiti/register`: `import.meta.resolve()` throws `ReferenceError: jitiESMResolve is not defined`

`jiti <script>`: `require.main === module` and `import.meta.main` are false for the entry script

Bare `import.meta` is not transformed, so helpers receive the wrapper's meta (a data: URL) and native resolve

normalizeParentURL guard tests the undefined identifier `filename`, so plain paths are never converted to file URLs

jiti's `import.meta.resolve` throws for nonexistent targets; Node and Bun do not

`jiti/native` passes a parent URL that Node only honors behind a flag

Concurrent `jiti.import()` calls evaluate a shared dependency twice

`module.children` misses cached and native dependencies

Module that fails during sync `require()` stays in the runtime cache with partial exports

Concurrent import() of a module that is still evaluating returns its partially evaluated exports

Import attributes (`with { type }`) are silently dropped in transformed modules

DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.

fs cache: a concurrent store can be read as a hit with NUL bytes (non-atomic writeFileSync)

interopDefault cache throws TypeError (Proxy invariant) after Object.defineProperty on an export

Slow resolution of `./foo.js` imports that point at `./foo.ts`

CJS module returns with two nested layers of `default`

Feedback from pi extension loader: lazy transform, bare aliases, native passthrough, cache invalidation

fsCache default: node_modules/.cache/jiti never resolves for file-path instance ids (silent TMP_DIR fallback)

`interopDefault`'s caching Proxy (#421) breaks ESM live bindings for mutable exports

[Bug]: jiti config import resolver in rspack fails to respect --perserve-symlinks / jiti gives no symlink-following customization options to fix this

Pass `filename` to the Babel transform

tsconfigPaths behaves not the same as tsc

Bug: `interopDefault` proxy returns bound functions, breaking native `await using` (Node 24+)

Give an error when a default import failed