Andrew Bradley

Unfortunately node only allows getting into the ESM loading path via `--loader`

Actually that may not be entirely true. There are caveats and limitations but I think the `vm` module might have something?

I suppose one other thing worth clarifying, this is technically incorrect, though it may not be worth changing: > This occurs because ts-node does not support any module syntax other...

Yes, apologies I forgot to include a link. Here it is: https://webpack.js.org/configuration/configuration-languages/

Linking to the issue and PR that add cts support to interpret: https://github.com/gulpjs/interpret/issues/89 https://github.com/gulpjs/interpret/issues/90

Follow-up from my comment https://github.com/nodejs/node/issues/43818#issuecomment-1196849289 Are you interested in getting sucrase support added as a dedicated `"sucrase": true` flag in ts-node? It can still live as a separate package, so...

I left responses to everything above. One other thing not mentioned: Today ts-node overrides a few of your compiler options to "just work." For example we force-enable sourcemaps so that...

True, the other solutions only support buttons at the top and bottom of the inspector, not in the middle. When you need a "dummy" field to put decorators on, what...

I see the memory leak on v8.12.0 but not on v10.11.0. This might be a node bug, considering that async_hooks was a preview feature in node 8.

Sweet, sounds great. I'm travelling for Thanksgiving all of today (driving yay) but I'll take a look at this tomorrow. On Nov 20, 2016 19:25, "Wallace Sidhrée" [email protected] wrote: >...