-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for .js files without internal TypeScript compilation #55
Comments
Being able to do this would help with another issue that I'm having with ts-node. I'm including Here's the ts-node issue on the topic: TypeStrong/ts-node#783 They closed the issue saying that Microsoft has to implement a workaround in TypeScript. However, Microsoft has indicated that they don't want to rewrite import paths. Thus resulting in a stalemate. In summary, ts-node is off-limits for me due to a variety of unsupported features. |
Another issue I noticed is that TestyTS currently seems to force TypeScript 3.9 for ts-node compilation, even though the stable version of 4.0 has been released already. Being able to compile TypeScript files externally should probably resolve this as well. |
Hi! I somehow didn't get notified you created an issue! I'll take a clsoe look at this as soon as possible. If you would like to make a pull request and fix this, that would also be welcome! |
Hello! Just a quick update: I haven't had time to take a look at this in particular because I've been working on setting up integration tests. Now that that's done, I should be able to make a repro and fix this. |
Hi, The latest beta version of TestyTs, 2.0.0-beta.5, now comes with the latest version of ts-node. This should fix the Thanks! |
Hi,
I'm currently using a beta feature from TypeScript 4.1 beta, which has a new flag in tsconfig.json called
noUncheckedIndexedAccess
.ts-node doesn't understand this yet, which is evident when I try to run
testyts
:Is it possible to use an external
tsc --watch
process and just point testyts at the compiled .js files?The text was updated successfully, but these errors were encountered: