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
All of our TypeScript code uses imports without extensions. Example:
import*asmodulefrom'./module';
This works because our code is in CommonJS; at compile time, TypeScript will know to look for module.ts or module.d.ts, at run-time Node will look for module.js.
Currently, ts-jest-resolver will not handle paths without extensions correctly: it will only replace known extensions with different ones, not try to add extensions to unqualified files.
I can write a PR to add this behavior. Would you accept it if I did?
The text was updated successfully, but these errors were encountered:
All of our TypeScript code uses
import
s without extensions. Example:This works because our code is in CommonJS; at compile time, TypeScript will know to look for
module.ts
ormodule.d.ts
, at run-time Node will look formodule.js
.Currently,
ts-jest-resolver
will not handle paths without extensions correctly: it will only replace known extensions with different ones, not try to add extensions to unqualified files.I can write a PR to add this behavior. Would you accept it if I did?
The text was updated successfully, but these errors were encountered: