Closed connorjclark closed 2 years ago
not possible because of breaking changes. What's the root issue? Normally you can have different versions of the same package in the project without problem, so what's up with ts-node?
I don't recall specifically but I am leaning on some newer feature in the latest ts-node, so having tests run with something different is a cause for concern. (I'm one of those people using ts-node in production too 😆 )
Closing since infeasible.
My project already is using ts-node (v10), but this package brings it's own (v7). Perhaps it'd be possible to set ts-node as a peer dep and defer to the user to bring in a specific version?