Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Native ESM support, possibly requiring integration with ts-node
See original GitHub issueIn ts-node we released experimental support for native ECMAScript modules. To do this we needed to implement a custom resolve() loader hook. It is a copy-paste of node’s built-in resolver, tweaked for our needs.
https://github.com/TypeStrong/ts-node/issues/1007
Is native ESM support on your radar? Do you have thoughts on how best to implement it for tsconfig-paths? I expect we will need to coordinate, since node only supports a single loader hook.
I see that the compiler itself can perform these resolutions via ts.resolveModuleName. Do you use that internally, or do you do something else?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:26
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I wanted to mention new solution created by @charles-allen 4 days ago (https://github.com/TypeStrong/ts-node/discussions/1450#discussioncomment-1806115)
Closing in favor of https://github.com/TypeStrong/ts-node/pull/1585 which will add native path mapping support to ts-node.