type changes not updated during watch mode

[unional]

Issue

When you make changes to the types, e.g. renaming a type, the changes cause the test to fail, even if the change actually works fine.

Need to quit jest watch and start again for the changes to be picked up correctly.

causes

My guess is that during rename, multiple files are affected and ts-jest only detect one file has been changed, so the cache of other files are not invalidated, thus containing outdated information.

This happens whenever I make changes to multiple files and save them at the same time.

Another example would be moving a type from one file to another.

Minimal repo

I encounter this in multiple situations. For example, https://github.com/unional/progress-str

To reproduce the issue, you need to run the test in watch mode (npm run watch in the repo above),
and then make some changes such as rename or move types.

[unional]

Note that this does not occur every time, but I encounter this about 3-4 times a day.
If I encounter again, I'll post more detail about how to reproduce this.

[nathanmarks]

Seeing this issue as well. It's really frustrating. I can even clear out a whole file that has types and it isn't picked up.

[antonovicha]

I stumble upon of similar issue. And I guess I have an explanation of what's going on.

As you may know TS type information only exists during development and removed upon compilation. Jest compiles files one by one and stores result in cache.

Now consider following example:

File1: type definitions
File2: imports File1

Run tests. All is OK. Jest will cache compiled File1 and File2.

Scenario 1:

Change File1 and break type (rename, change signature, etc.). What will happen?
File2: still the same, cached version is used. Therefore tests are green.

Scenario 2:

Now change File1 and File2. Save them both together.
File2: new, Jest will compile it.
File1: new, Jest will compile it. TS will pickup breaking change reporting an error.

Workaround: use --no-cache when running tests.

[aaw5017]

I am running into this problem also. Any updates?

[ahnpnl]

hi @unional @aaw5017 @antonovicha @nathanmarks would you please help us to test the fix ? You can download tgz file here and install it. Remember to clear cache before you run your tests

[unional]

Hi @ahnpnl , my current projects do no do type checks through jest anymore, because it slow me down unnecessary.

So my projects are not using ts-jest now. Since this will likely require bigger project to reproduce, I won't be able to help testing the fix at the moment. Thanks. 🌷

[kevinsimper]

I also experienced this, I made a minimal repository with steps to reproduce:

https://github.com/kevinsimper/jest-ts-jest-import-error

Steps to reproduce:

• run jest with watch $ npm test -- --watch
• go into src/add.test.ts and edit the import from add1 to add2 in both import and where the function is used
• see the error:

 FAIL  src/add.test.ts
 ● Test suite failed to run

 src/add.test.ts:1:10 - error TS2305: Module '"./add"' has no exported member 'add2'.

1 import { add2 } from "./add";

• go into ./add and fix the function to be called add2.
• see that the jest runner still say the same error
• restart the runner and see it works now

[sgronblo]

I have been frustrated by this too. Would love to know if you find a solution.

[distante]

At least I now know it is not a problem with my environment.

[sylvainar]

omg i just had this problem, arrives here after googling, saw you fixed it 5 hours ago: awesome! 🎉

[sgronblo]

Nice, which version will contain this fix and when can you release it?

[ahnpnl]

v27 :) currently working on support jest 27 too. So when jest 27 is out, ts-jest will follow

[bidoubiwa]

Not sure it is linked to this issue, but at my first jest --watch after clearing jest cache I receive the expected typescript errors of
TS2532: Object is possibly 'undefined'.

When saving a test file (without resolving any of the type errors), tests are run again and all TS2532: Object is possibly 'undefined'. errors disappear and tests are now all successful.

I need to relaunch the tests after yarn --clearCache for the type errors to appear again.

If this is not related I can create an issue about it.

[ahnpnl]

@bidoubiwa are you using next tag ? The error you saw should point to somewhere. If it points to node_modules/ts-jest then something with ts-jest, if not then something with your codebase.

[bidoubiwa]

Unfortunately, I'm not able to see where the error comes from.

    tests/typed_search_tests.ts:266:13 - error TS2532: Object is possibly 'undefined'.

    266             response.hits[0]?._matchesInfo?.title[0]?.start === 6

I tried changing the tag to next (do you mean in the tsconfig.json?) but it did not change the problem. As soon as I refresh the tests this error disappears.

[MartinJohns]

@bidoubiwa Without seeing the code it's difficult to figure out what could possible be undefined. In the line you posted it could be response.hits or response.hits[0]?._matchesInfo?.title, so try to use the optional chaining operator here too:

response.hits?.[0]?._matchesInfo?.title?.[0]?.start

Your error does sound a lot like the one from this issue. You're having a TypeScript error, but upon further runs the error is not shown anymore (despite still being present).

The reference to next refers to a previous version of ts-jest: https://www.npmjs.com/package/ts-jest/v/27.0.0-next.4

[bidoubiwa]

Thanks a lot, @MartinJohns, I'm not sure I understand your last sentence.

Does this mean that after the next release of ts-jest, errors will still be present without having to clear the cache between each test?

[mlynch]

Still seeing this on ts-jest 27.0.7 and jest 27.2.5. During watch, ts-jest is throwing an error saying that a certain file doesn't export a type, but it does. When I kill the watch and restart it, the issue is fixed.

[GerkinDev]

Having this too. Might this issue be reopened ?

[mshahoyi]

I have this issue too with ts-jest 27.0.7

[argos83]

Hi @ahnpnl , I'm not sure if this wasn't actually fixed or if it is a regression. I recall this not being an issue a few months ago. There are some other issues related to this. Shall I create a new one? Or could you to reopen this?

What I experience is that type changes are not picked up anymore when running jest --watch. Passing --no-cache is not fixing it either.
I've tested with the currently latest version 27.0.7.

[Mazata]

I'm also experiencing this issue with version 27.2.0
This doesn't only apply to types though. If I change a function signature in an imported file, the test doesn't pick up on that change until I kill the test watcher and re-run it
Using the --no-cache flag doesn't help me either.
Upon request I'm happy to make a small repo to reproduce the error

[excitement-engineer]

Also running into this issue with the most recent version of ts-jest (28.0.3), please consider reopening this issue until it is fixed. Thanks a lot.

[GvidasP]

Also running into this issue with the most recent version of ts-jest (28.0.3), please consider reopening this issue until it is fixed. Thanks a lot.

Running into the same issue as well.

[RadovanBednar]

I'm experiencing this issue in a fresh project with jest 29.3.1 and ts-jest 29.0.3. It's very frustrating, makes "watch" mode unusable 😞

[alexgorbatchev]

Also seeing the same issue.

[jsorant]

Same issue here, very frustrating as this feature really makes TDD fluent...

[tobyhinloopen]

ts-jest 29.0.5 here, same issue

[Hagith]

Just noticed the same problem, ts-jest 29.0.5

[dncrews]

Hey @ahnpnl. I just wanted to check in on this. Any chance of getting this reopened? It seems to be a consistent issue, so it would be great to at least have it acknowledged, even if we don't have a solution.

[saiichihashimoto]

Still happening on newest versions, do we have tests to ensure this specific issue is fixed? It feels like either we're not ensuring the right fix is occurring, or regressions are slipping through.