Caching of babelrc file

[bondom]

🐛 Bug Report

In our project we use aliases. To be able to resolve these aliases in tests we use babelrc file.
But when we add new alias or delete old one(change babelrc file), and then run tests again, jest doesn't know about our changes to babelrc file.
Only after we run jest --clearCache, changes to babelrc are visible to jest

To Reproduce

1. Run test which uses alias, it should run successfully
2. Delete alias from babelrc file.
3. Run test again, it runs successfully again - bug
4. Run jest --clearCache,
5. Run test again, it fails

Expected behavior

Changes to babelrc should be visible to jest without clearing of cache

Link to repl or repo (highly encouraged)

https://github.com/bondom/ts-jest-bug

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: macOS High Sierra 10.13.4
    CPU: x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 8.10.0 - /usr/local/bin/node
    npm: 6.0.1 - /usr/local/bin/npm
  npmPackages:
    @types/jest: ^22.2.3 => 22.2.3
    jest: ^22.4.3 => 22.4.3

Note: this issue is just copy of kulshekhar/ts-jest#524

[SimenB]

Can you reproduce using just Jest? babel-jest has to my knowledge no issues cache-busting a json-based babel config (we have an issue somewhere for JS based config, but that doesn't apply here)

[bondom]

@SimenB Just tried it using just Jest. It works as expected without bugs. So it is issue of ts-jest

[SimenB]

Awesome, thanks!

[jamietre]

we have an issue somewhere for JS based config, but that doesn't apply here

@SimenB This issue is still open which is for just .babelrc (json): #3772

Do you believe this is fixed? I'm also having trouble with this, and it looks like the cache key still does not include either relevant environment variable.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.