ts-node
ts-node copied to clipboard
TypeStrong
TypeScript execution and REPL for node.js
### Search Terms Slow import Long time import ### Expected Behavior Speed regardless of the indication of `allowJs` ### Actual Behavior Import without `allowJs` option takes about 0.5 ms Import...
Since TypeScript 5.0, stage 3 decorators had become the default while `experimentalDecorators` had become the legacy standard. However, with SWC enabled, ts-node doesn't work correctly with stage 3 decorators. This...
### Desired Behavior As part of a prebuild step in a project of mine, I'm reading multiple `tsx` files, inserting a small snippet, and running them through `ts-node --eval`. I...
I've got a `*.ts` file which imports a `*.tsx` file. The pasted GitHub Actions workflow is a self-contained reproducer and completes successfully. But if I remove `sed -i 's@"type": "module",@@'...
First commit fixes the bug as described. Second commit simplifies comparison chain by using De Morgan's law. **Note**: as described on the referred issue, there's an exception being printed with...
### Search Terms - swc - ES2024 - ES2023 ### Expected Behavior - SWC since [version 1.8.0](https://github.com/swc-project/swc/pull/9700) (2024-11-04) supports ES2023 and ES2024 - Once using `ts-node` with `swc` having a...
I'm looking for companies or individuals who benefit from `ts-node` and would like to see continued updates to sponsor work on this package. I'm more than happy to coordinate with...
Resolves https://github.com/TypeStrong/ts-node/issues/2160 This PR adds ES2023 and ES2024 as SWC supported targets. SWC since https://github.com/swc-project/swc/pull/9700 (2024-11-04) supports ES2023 and ES2024
Environment Information - Node.js version: 20.19.1 - ts-node version: [email protected] - TypeScript version: [email protected] - OS: macOS tsconfig.json settings: { "compilerOptions": { "module": "NodeNext", "moduleResolution": "NodeNext", "target": "ES2022", "esModuleInterop": true,...
### Search Terms `ts-node`, `ESM`, `exports`, `default export`, `import`, `require`, `wrong types` ### Expected Behavior When using `ts-node` in ESM mode, it should correctly resolve type definitions from the `import.types`...
