Following Typescript recipe with ts-node loader, with a type issue causes OOM/timeout errors (circumstantial) #3133
Unanswered
danielgormly
asked this question in
Q&A
Replies: 1 comment 2 replies
-
This is a problem with |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What you're trying to do
Great tool, though we're having a problem in some of our projects that rely on ts-node loader. We know there's a timeout (or JS OOM error depending on file) but we don't know why without thorough investigation. We are following Typescript recipe in docs/recipes/typescript.md and using native ESM modules.
What happened
When there is a type issue in a test, adding number of lines to that test file appears to exponentially affect memory usage and test time.
What you expected to happen
Test(s) fails
I am testing this on my Macbook Air M1. I have tested with Node 18.12.0 and Node 16.17.
Minimal Reproduction:
package.json
ava.config.js
tsconfig.js
working.spec.ts
broken.spec.ts
Beta Was this translation helpful? Give feedback.
All reactions