ts-node has a –transpile-only (or -T) argument. It will ignore all type errors and just build your project. My 2022 suggestion for this to set up esbuild instead. Not a plug and play experience, but extremely fast. We use esbuild for (constant) building during development, and rely on other tools to report type errors.
i’m using same configuration like yours but it only work when i downgrade to ts-node@9, and then i tried this option in my .mocharc.json and now it’s working as i expected { “extensions”: [“ts”], “spec”: [“**/*.spec.*”], “node-option”: [ “experimental-specifier-resolution=node”, “loader=ts-node/esm” ] }
Use the –esm switch for ts-node. Eg ts-node –esm index.ts This requires you to have the module to set to one of the newer ones (like nodenext or node16) and moduleResolution also set to a newer method, in your tsconfig.
You need to run: $ npm install @types/node –save-dev If you need additional information you can refer to the NodeJS QuickStart in the TypeScript Deep Dive by Basarat.
In my case, I was facing this error for react. I fixed it by changing my import style from import React from ‘react’; to import * as React from ‘react’;
The Error Warning: To load an ES module, set “type”: “module” in the package.json or is caused by the following Bug in ts-node: https://github.com/TypeStrong/ts-node/issues/935 The Bug is closed, and there is a proposal to solve it, but it is still open: https://github.com/TypeStrong/ts-node/issues/1007 I don’t need “type”: “module” in package.json. In tsconfig.json, I’m using using “module”: … Read more
After a lot of searching, I found this solution works perfect: https://github.com/TypeStrong/ts-node/issues/922#issuecomment-673155000 Just add a “ts-node” block to your tsconfig.json file as below: { “ts-node”: { “compilerOptions”: { “module”: “commonjs” } }, “compilerOptions”: { “module”: “esnext” } } And it has been documented in the ts-node official page “Via tsconfig.json” part. This saved hours of … Read more
You did not provide your script, so I can only guess at how you are extracting the arguments. This is how I have made it work with my own test script args.ts: const a = process.argv[2]; const b = process.argv[3]; const c = process.argv[4]; console.log(`a: ‘${a}’, b: ‘${b}’, c: ‘${c}’`); Called from package.json like this: … Read more
With ts-node 5.0.0 you no longer pass the –inspect flag the same way. The suggested way is node –inspect -r ts-node/register path/to/ts. For example: nodemon –watch src/**/* -e ts,json –exec node –inspect-brk -r ts-node/register src/app.ts see https://github.com/TypeStrong/ts-node/issues/537
Note: for a working example with nodemon, skip to the second section of my answer. If you mean that once you compiled the files and run the application, the modules are not found, then have a look at this thread: Module path maps are not resolved in emitted code “paths” is designed for use with … Read more