Open kanjieater opened 4 years ago
In my case I had a running instance in the background - killed my node processes and the error went away. Hope it helps!
I have the same issue when application is already restarting and a file is modified at the same time.
any idea on how to fix this? i think @matiaschileno is right about how this happens
I couldn't reproduce this in tests. You may try to add test that reproduce the issue.
I just experienced this as well, and I think it's the same scenario as @matiaschileno
+1 encountering this due to saving files multiple times while app is still restarting
+1
I can also reproduce this if the node process crashed and a file changed.
Basically I'm testing uncaught promises in my app. When it happens, node crashes, but ts-node-dev does not report it. And if I edit a file, I have the EPIPE error in an infinite loop.
Trying to narrow down why I'm seeing this error:
It seems like it is coming directly from ts-node-dev.
I've seen a handful of different root causes, and my current theory is they seem to happen when the app is starting up, but detects a change: Example 2:
at Object.<anonymous> (/Users/x/IdeaProjects/asdf/node_modules/graphql/type/definition.js:57:40)
Example 3:
at Object.<anonymous> (/Users/asdf/IdeaProjects/x/node_modules/rxdb/dist/lib/plugins/encryption.js:16:41)