You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"jest": "^29.7.0",
"ts-jest": "29.2.3",
"typescript": "^5.7.2",
and the following code works fine when executed in a test:
const myJsModule = '/some/absolute/file.js';
const obj = await import(`file://${myJsModule}`);
but if I upgrade to "ts-jest": "29.2.4" then my dynamic import starts to say:
Cannot find module 'file:///some/absolute/file.js' from 'test/repro.test.ts'.
but if I remove the 'file://' prefix then it works again.
This 'file://' prefix is required on windows when running through node and not jest... so it definitely should work.
Version
29.2.4
Steps to reproduce
Inside of my package.json I have dependencies at
but if I upgrade to "ts-jest": "29.2.4" then my dynamic import starts to say:
but if I remove the 'file://' prefix then it works again.
This 'file://' prefix is required on windows when running through node and not jest... so it definitely should work.
Why are things broken with 29.2.4?
For more info about my usecase, the actual code in question that we are trying to maintain is over at https://github.com/forcedotcom/code-analyzer-core/blob/dev/packages/code-analyzer-eslint-engine/src/strategy.ts#L235
Expected behavior
I wouldn't expect things to fail when upgrading from 29.2.3 to 29.2.4 or greater.
Actual behavior
See above.
Debug log
See above.
Additional context
No response
Environment
The text was updated successfully, but these errors were encountered: