cache is not cleared after tsconfig.json changes when using tsimp

[andriyor]

i had such error

❯ tsimp src/esm/usage.ts
(node:98619) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
src/esm/usage.ts:3:1 - error TS2584: Cannot find name 'console'. Do you need to change your target library? Try changing the 'lib' compiler option to include 'dom'.

3 console.log(sum(2, 8));

after lib propperty change in tsconfig.json i had the same error

"lib": ["dom"],

and only after deleting of .tsimp it fixed

[andrew0]

It seems like in general tsimp doesn't clear the cache for any changes to a file's dependency tree (including the tsconfig). For example:

1. Create two files, "foo.ts" and "bar.ts":

   foo.ts

   export {};

   bar.ts

   import {foo} from './foo.js';
   
   foo();

2. Run node --import=tsimp/import bar.ts:

   bar.ts:1:10 - error TS2305: Module '"./foo.js"' has no exported member 'foo'.
   
   1 import { foo } from './foo.js';
           ~~~
   
   bar.ts:1
   import { foo } from './foo.js';
           ^
   
   SyntaxError: The requested module './foo.js' does not provide an export named 'foo'
       at ModuleJob._instantiate (node:internal/modules/esm/module_job:131:21)
       at async ModuleJob.run (node:internal/modules/esm/module_job:213:5)
       at async ModuleLoader.import (node:internal/modules/esm/loader:308:24)
       at async loadESM (node:internal/process/esm_loader:42:7)
       at async handleMainPromise (node:internal/modules/run_main:66:12)
   

3. Update foo.ts implementation to fix TypeScript error:

   foo.ts

   export function foo() {
     console.log('hello world');
   }

4. Run node --import=tsimp/import bar.ts again, and it still shows the old error:

   bar.ts:1:10 - error TS2305: Module '"./foo.js"' has no exported member 'foo'.
   
   1 import { foo } from './foo.js';
           ~~~
   
   hello world
   

After clearing the .tsimp cache, the type error goes away.

[NoahAndrews]

@andrew0 I filed #20 for that issue. That being said, it doesn't seem to actually be an issue with the on-disk cache (all you need to do is restart the daemon, not delete the cache).