It seems Jest uses its own require (jestjs/jest#5120) which we're not able to test require's cache using Jest. I guess we could just update cosmiconfig without adding a test in this case.

You can run jest.resetModules(), but I'm now sure how cosmiconfig caches. If it's just delete require.cache[thing] then it's always empty when running through Jest, so a resetModules should work

I thought about it, but if Jest hold caches, the test will always be passed if we jest.resetModules() regardless the bug is fixed in cosmiconfig or not.

Ref: https://github.com/davidtheclark/cosmiconfig/pull/158/files#diff-e53a183cc3cc3a312532c73d45ca29cb

Ah, indeed.

I have some nefarious plans at some point to add support for require.cache properly (including delete, Proxy makes it quite straight forward), but it's super low pri at the moment

removed the test!

Thanks!