react-transform-hmr is being required in jest tests?

[gaearon]

react-transform-hmr is being required in jest tests?

[jonaswindey]

For later versions of Jest, you also have to remove the cache folder configured in jest /"cacheDirectory" in package.json (just wasted 2 hours looking for it)

If you don't specify the cacheDirectory the folder is at /private/var/folders/lm/x4_bq9sd24d9_vjs84wdl9cr0000gp/T/jest/jest-transform-cache--Users-jonas-Development-3nit-io-aa63b6391f6782d2e445325c13c1bc66 (depending on your environment) , so just put "cacheDirectory": "/jest-cache" under the jest key of your package.json and you'll be able to remove that when necessary.

[gaearon]

You're probably running tests without any NODE_ENV, so Babel assumes "development" and enables it per .babelrc.

[buob]

I suspected that, so I changed the script to be NODE_ENV=test jest, and even got rid of the config in .babelrc so it wouldn't have anything to reference react-transform-hmr, but it's still happening. Even the explicit export NODE_ENV=test before running the tests didn't affect it. 😕

[gaearon]

Maybe there's some weird caching going on?
If you removed it from config, where else can it come from?
You can delete the package to be sure, and look what code crashes.

[gaearon]

Anyway, this looks like an issue in your setup, rather than an issue with this project.

[joshblack]

@buob did you ever resolve this issue? I'm having the same problem when setting up jest with react-transform-hmr. Changing NODE_ENV doesn't stop the Runtime Error that jest throws, and removing it from babelrc also doesn't help.

If you remove the react-transform-hmr module from the node_modules folder then it just says that it can't find that module.

[buob]

A colleague of mine ended up figuring it out because of this issue - #5 (comment)

We moved our .babelrc content to webpack config.

[obourne]

I had the same issue and ended up removing .babelrc too but jest didn't stop using react-transform-hmr until I manually deleted the .haste_cache dir from the jest-cli node_modules dir

[joshblack]

@obourne that is what tripped me up for the longest time. Thanks for writing it down, I'm sure whoever comes across this issue next will thank you for it.