Error: unknown file extension .ts #1062

Thomas1664 · 2020-05-30T10:13:25Z

Expected Behavior

Load typescript files

Actual Behavior

When I try to execute a typescript file I get the following error message:
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /home/$USERNAME/$PATH_TO_DEV_FOLEDER/index.ts
at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15)
at Loader.getFormat (internal/modules/esm/loader.js:113:42)
at Loader.getModuleJob (internal/modules/esm/loader.js:243:31)
at Loader.import (internal/modules/esm/loader.js:177:17)

Steps to reproduce the problem

launch ts-node index.ts

Minimal reproduction

Specifications

ts-node version: v8.10.2 (installed global)
node version: v14.3.0
TypeScript version:v3.9.3 (installed global)
tsconfig.json, if you're using one:

{}

Operating system and version: Windows 10 Version 2004
If Windows, are you using WSL or WSL2?: Yes, Ubuntu 20.04 LTS in WSL2

The text was updated successfully, but these errors were encountered:

cspotcode · 2020-06-02T16:58:50Z

ESM stuff? You might have better luck on our ESM thread. Or post a complete reproduction so someone else can debug.

alexcochran · 2020-06-06T14:49:35Z

I'm having the same issue.

λ npx ts-node src/app.ts
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for C:\Users\$USER\$PATH_TO_DEV_FOLDER\src\app.ts
    at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15)
    at Loader.getFormat (internal/modules/esm/loader.js:113:42)
    at Loader.getModuleJob (internal/modules/esm/loader.js:243:31)
    at Loader.import (internal/modules/esm/loader.js:177:17)

Aguinaldo-Alberto-Naldo · 2020-06-21T13:43:59Z

Estou tendo o mesmo problema também

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for www\server\src\server.ts at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15) at Loader.getFormat (internal/modules/esm/loader.js:113:42) at Loader.getModuleJob (internal/modules/esm/loader.js:243:31) at Loader.import (internal/modules/esm/loader.js:177:17)

cspotcode · 2020-06-21T16:10:17Z

My earlier suggestion should point you in the right direction.

…

On Sun, Jun 21, 2020, 9:44 AM AguinaldoAlberto ***@***.***> wrote: Estou tendo o mesmo problema também TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for www\server\src\server.ts at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15) at Loader.getFormat (internal/modules/esm/loader.js:113:42) at Loader.getModuleJob (internal/modules/esm/loader.js:243:31) at Loader.import (internal/modules/esm/loader.js:177:17) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1062 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAC35OCO5M3WUUNXSLA4YS3RXYFCVANCNFSM4NOUHHYQ> .

clinkadink · 2020-06-28T12:35:00Z

Remove "type": "module" from package.json

SaintPhill · 2020-07-16T09:56:58Z

Remove "type": "module" from package.json

If remove module type, you cannot use imports in your .ts files

Thomas1664 · 2020-07-16T10:03:21Z

I must disagree. In Angular projects, there is no "type": "module" in package.json and import synthax works fine. Try to set "module": "es2020" in tsconfig.json

SaintPhill · 2020-07-16T10:06:39Z

I must disagree. In Angular projects, there is no "type": "module" in package.json and import synthax works fine. Try to set "module": "es2020" in tsconfig.json

nope, same problem with import.
"Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension."

Thomas1664 · 2020-07-17T20:04:21Z

I created a template repo which can be used by anyone who has trouble initializing ts-node.

cspotcode · 2020-07-29T02:23:46Z

Closing as this is not a ts-node bug. If you want to use node's native ESM support, which is currently experimental, then you can use ts-node's experimental ESM loader hook. See #1007 for details.

paxperscientiam · 2020-12-10T17:42:02Z

@clinkadink thanks, that did it for me

cspotcode · 2020-12-10T19:46:57Z

We've enabled the discussion forum for questions like this one.

https://github.com/TypeStrong/ts-node/discussions

We're trying to keep the issue tracker limited to actionable tasks, so contributors can focus on making fixes and improvements to ts-node.

Since this is not a bug and nothing needs to change in ts-node, it's not actionable, so it was closed. Discussions, on the other hand, are the perfect place to ask advice, share guides, and help with project configuration.

Another good thing about the discussion forum: you don't need to fill out an issue template.

a-h · 2021-01-26T11:29:49Z

This stack overflow answer helped me: https://stackoverflow.com/questions/63445821/ts-node-execute-typescript-with-module-import-and-module-defined

Updating my tsconfig.json to migrate from "module": "es6" to "module": "commonjs" allowed me to run my TypeScript file.

kseebrinegar · 2021-02-15T01:07:39Z

@a-h Thank you bro! you the man!

buzuosheng · 2021-03-15T09:40:44Z

Remove "type": "module" from package.json

If remove module type, you cannot use imports in your .ts files

I'm having the same issue. how to fix, thx

itcat99 · 2021-04-14T02:09:18Z

This stack overflow answer helped me: https://stackoverflow.com/questions/63445821/ts-node-execute-typescript-with-module-import-and-module-defined

Updating my tsconfig.json to migrate from "module": "es6" to "module": "commonjs" allowed me to run my TypeScript file.

Thanks! it's useful.

Rollingegg · 2021-04-14T09:01:30Z

From #1007, use node --loader ts-node/esm ./my-script.ts if your tsconfig.json contains "module": "commonjs"

shanoysinc · 2021-04-29T22:42:01Z

I remove type: module from package json and it work

Abeautifulsnow · 2021-05-17T06:50:47Z

This stack overflow answer helped me: https://stackoverflow.com/questions/63445821/ts-node-execute-typescript-with-module-import-and-module-defined

Updating my tsconfig.json to migrate from "module": "es6" to "module": "commonjs" allowed me to run my TypeScript file.

This solution resolves my two problems which are "import" syntax-error outside module and unknown file extensions ".ts"!!! Thank you very much for saving my time. 😁

iway1 · 2021-06-18T13:01:33Z

Add this to the tsconfig.json:

  "compilerOptions": {
    "esModuleInterop": true
  }

and make sure to start the server with ts-node:

ts-node my_ts_node_server.ts

It is crazy how hard it was for me to find this. This will allow you to use imports as well as use typescript.

Mehak-Mehta · 2021-06-18T13:19:31Z

Add this to the tsconfig.json:
  "compilerOptions": {
    "esModuleInterop": true
  }
and make sure to start the server with ts-node:
ts-node my_ts_node_server.ts
It is crazy how hard it was for me to find this. This will allow you to use imports as well as use typescript.

Yup that works!!

Cobular · 2021-08-02T01:17:29Z

From #1007, use node --loader ts-node/esm ./my-script.ts if your tsconfig.json contains "module": "commonjs"

Real quick follow up to this - running with this makes my code ~8x slower than ts-node by itself with changed options or just using tsc and node, and that's testing the same exact function 10 times in a loop to mitigate the effects of the typescript JIT compilation times. Hopefully this is useful to someone?

goldEli · 2021-10-08T09:49:48Z

Remove "type": "module" from package.json

If remove module type, you cannot use imports in your .ts files

set the value of module to commonjs in tsconfig.json, it works for me.

{
"module": "commonjs",  
}

iseekTo · 2021-10-15T07:27:09Z

ts-node --skip-project scripts/yourFile.ts

karlhorky · 2021-10-22T11:23:11Z

For anyone who is running into this issue on CI or on Node.js 16.12.0, it seems like this latest version has made some changes to the hooks API 😱

https://github.com/nodejs/node/releases/tag/v16.12.0

Also mentioned here:

#1007 (comment)

cspotcode · 2021-10-22T17:43:43Z

Supported by ts-node 10.3.1

xgqfrms · 2023-03-22T10:26:21Z

ts-node error ❌

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"

ESM solution ✅

"type": "module", & ts-node-esm

{
  "name": "patch-package-in-action",
  "version": "1.0.0",
  "description": "patch-package in action",
  "main": "./src/app.ts",
  "type": "module",
  "scripts": {
    "app-esm": "npx ts-node-esm ./src/app.ts",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/web-fullstack/patch-package-in-action.git"
  },
  "author": "xgqfrms",
  "license": "MIT",
  "dependencies": {
    "lodash-es": "^4.17.21",
    "typescript": "^5.0.2"
  },
  "devDependencies": {
    "@types/lodash-es": "^4.17.7",
    "app-node-env": "^1.4.7",
    "rimraf": "^4.4.0",
    "ts-node": "^10.9.1"
  }
}

{
  "compilerOptions": {
    "target": "ESNext",
    "module": "ESNext",
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "strict": true,
    "skipLibCheck": true
  }
}

lodash-es

// ./src/app.ts

import {toString} from "lodash-es";

type Obj = {
  [key: string]: any;
}

const obj: Obj = {
  name: 'xgqfrms',
  country: 'China',
  language: 'zh-hans',
};

const str = toString(obj);
console.log(`toString =`, str1);

refs

https://typestrong.org/ts-node/docs/imports/

TypeStrong/ts-node#1062 (comment) https://www.cnblogs.com/xgqfrms/p/17245062.html

leonasdev · 2023-04-10T04:18:55Z

I just rm -rf dist and tsc & node dist/index.js again, then it works.

VladBrok · 2023-06-01T07:41:32Z

What worked for me is ts-node --esm <filename>. No esModuleInterop or package.json changes

@dfenerski thanks

neerajkumar161 · 2023-07-02T10:01:45Z

"ts-node": {
  "esm": true
}

This worked for me. Thanks, @retrotechie 🚀

JuYiYang · 2023-08-19T09:52:41Z

Remove "type": "module" from package.json
remain invalid

88brmig · 2023-08-23T19:52:56Z

if your tsconfig.json contains "module": "ESNext". I have used the below script in my package.json. It worked.
 "start": "nodemon -e ts -w ./src -x npm run watch:serve",
 "watch:serve": "node --loader ts-node/esm src/server.ts",

Using node 20 with sveltekit, this works

JuYiYang · 2023-08-24T06:22:41Z

if your tsconfig.json contains "module": "ESNext". I have used the below script in my package.json. It worked.
 "start": "nodemon -e ts -w ./src -x npm run watch:serve",
 "watch:serve": "node --loader ts-node/esm src/server.ts",
Using node 20 with sveltekit, this works

Thank you😘

jhonatanAlanFerreira · 2023-12-07T13:59:07Z

I need "type": "module" in package.json
npx tsx ./file.ts worked for me

quantuminformation · 2023-12-11T15:44:59Z

same error in 2023

anyone code a tsx launch file for vscode that allows debugging?

arsinclair · 2023-12-16T16:44:32Z

If you suddenly started getting this issue, this might be the cause: #2094

ejas404 · 2024-01-07T08:25:58Z

Add this to the tsconfig.json:
  "compilerOptions": {
    "esModuleInterop": true
  }
and make sure to start the server with ts-node:
ts-node my_ts_node_server.ts
It is crazy how hard it was for me to find this. This will allow you to use imports as well as use typescript.

Remove "type": "module" from package.json

If remove module type, you cannot use imports in your .ts files

for using esm add these
"compilerOptions": {

"module": "CommonJS",                                
"esModuleInterop": true,

}

it worked for me
if you face importing .ts extension

add this to your compilerOptions
"allowImportingTsExtensions": true,

Nb : Option 'allowImportingTsExtensions' can only be used when either 'noEmit' or 'emitDeclarationOnly' is set.ts
you have to set one of the true with it

arsinclair · 2024-01-08T09:59:24Z

for using esm add these

"module": "CommonJS",

That's not true. ESM and CJS (CommonJS) are two different things, changing module to CommonJS will make tsc produce CommonJS code.

jamesrr39 · 2024-01-10T23:16:20Z

I got this same error (Unknown file extension ".ts"), trying to run a typescript script with ts-node 10.9.1 and Node 20.10. I couldn't find a solution unfortunately (I tried "esModuleInterop": true in tsconfig), but running the script through tsx worked, so I ended up migrating from ts-node to tsx.

I find it really odd that .ts files are not recognised by default. Surely ts-node should know how to handle .ts files?

Rush · 2024-01-11T18:52:44Z

This is what worked for me. Not even ts-node-esm worked.

node --experimental-specifier-resolution=node --loader ts-node/esm file.ts

Let me just say that the entire ESM situation in Node.JS is a catastrophe. It created so much pain, incompatibility, lost hours. I don't understand why some decisions were made that contributed to this pain. It's probably not as bad as Python2 and Python3 but very close!

…ability to compile code TypeStrong/ts-node#1062 (comment)

…1977) This pull request resolves #1926 and prevents issues like it from happening in the future ## Rationale for this PR This PR changes the TypeScript execution package for use in scripts like `build:registry` from `ts-node` to `tsx`. This is because `ts-node` has many difficult quirks to work through (and is slow). In addition, it also has a difficult to understand error for newcomers that *is* reproducible. ### The ts-node error As shown in #1926, using `ts-node` (specifically in `build:registry`) results in this error: `Unknown file extension ".ts" for /ui/apps/www/scripts/build-registry.ts`. There are many issues in the `ts-node` repository documenting this problem: * TypeStrong/ts-node/issues/1062 * TypeStrong/ts-node/issues/2033 * TypeStrong/ts-node/issues/1997 Switching the typescript-in-node system to `tsx`, which uses esbuild under the hood, resolves this error. This PR shouldn't affect tests, representation, etc. and is merely a change of build tools. There is no urgent need to merge this. I accidentally deleted the head repository on #1937. That will not happen again.

C0D3O · 2024-02-22T17:44:55Z

for me worked the opposite ( updated node to the latest 21.x version )
the ts-node config part in tsconfig.json

"ts-node": {
		"esm": false,
		"compilerOptions": {
			"module": "NodeNext"
		}
	},

eminoda · 2024-04-12T02:23:23Z

tsconfig.json

{
  "compilerOptions": {
    "module": "ESNext", // tell tsc complier use esm module
    "moduleResolution": "Node10", // find file use CommonJS require
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "outDir": "dist"
  },
  "include": ["src/**/*"]
}

package.json

"type": "module",

…#1977) This pull request resolves #1926 and prevents issues like it from happening in the future ## Rationale for this PR This PR changes the TypeScript execution package for use in scripts like `build:registry` from `ts-node` to `tsx`. This is because `ts-node` has many difficult quirks to work through (and is slow). In addition, it also has a difficult to understand error for newcomers that *is* reproducible. ### The ts-node error As shown in #1926, using `ts-node` (specifically in `build:registry`) results in this error: `Unknown file extension ".ts" for /ui/apps/www/scripts/build-registry.ts`. There are many issues in the `ts-node` repository documenting this problem: * TypeStrong/ts-node/issues/1062 * TypeStrong/ts-node/issues/2033 * TypeStrong/ts-node/issues/1997 Switching the typescript-in-node system to `tsx`, which uses esbuild under the hood, resolves this error. This PR shouldn't affect tests, representation, etc. and is merely a change of build tools. There is no urgent need to merge this. I accidentally deleted the head repository on #1937. That will not happen again.

hellznrg · 2024-06-04T09:54:43Z

I got this same error (Unknown file extension ".ts"), trying to run a typescript script with ts-node 10.9.1 and Node 20.10. I couldn't find a solution unfortunately (I tried "esModuleInterop": true in tsconfig), but running the script through tsx worked, so I ended up migrating from ts-node to tsx.

I find it really odd that .ts files are not recognised by default. Surely ts-node should know how to handle .ts files?

Switching to tsx was the only thing that worked for me. Now it's as simple as yarn tsx . and BOOM. Not sure what the problem with ts-node is. It's defintely a ts-node problem.

…hadcn-ui#1977) This pull request resolves shadcn-ui#1926 and prevents issues like it from happening in the future ## Rationale for this PR This PR changes the TypeScript execution package for use in scripts like `build:registry` from `ts-node` to `tsx`. This is because `ts-node` has many difficult quirks to work through (and is slow). In addition, it also has a difficult to understand error for newcomers that *is* reproducible. ### The ts-node error As shown in shadcn-ui#1926, using `ts-node` (specifically in `build:registry`) results in this error: `Unknown file extension ".ts" for /ui/apps/www/scripts/build-registry.ts`. There are many issues in the `ts-node` repository documenting this problem: * TypeStrong/ts-node/issues/1062 * TypeStrong/ts-node/issues/2033 * TypeStrong/ts-node/issues/1997 Switching the typescript-in-node system to `tsx`, which uses esbuild under the hood, resolves this error. This PR shouldn't affect tests, representation, etc. and is merely a change of build tools. There is no urgent need to merge this. I accidentally deleted the head repository on shadcn-ui#1937. That will not happen again.

…#1977) This pull request resolves #1926 and prevents issues like it from happening in the future ## Rationale for this PR This PR changes the TypeScript execution package for use in scripts like `build:registry` from `ts-node` to `tsx`. This is because `ts-node` has many difficult quirks to work through (and is slow). In addition, it also has a difficult to understand error for newcomers that *is* reproducible. ### The ts-node error As shown in #1926, using `ts-node` (specifically in `build:registry`) results in this error: `Unknown file extension ".ts" for /ui/apps/www/scripts/build-registry.ts`. There are many issues in the `ts-node` repository documenting this problem: * TypeStrong/ts-node/issues/1062 * TypeStrong/ts-node/issues/2033 * TypeStrong/ts-node/issues/1997 Switching the typescript-in-node system to `tsx`, which uses esbuild under the hood, resolves this error. This PR shouldn't affect tests, representation, etc. and is merely a change of build tools. There is no urgent need to merge this. I accidentally deleted the head repository on #1937. That will not happen again.

Thomas1664 changed the title ~~Error: unknown file extension.ts~~ Error: unknown file extension .ts May 30, 2020

cspotcode added the needs more info label Jun 2, 2020

cspotcode closed this as completed Jul 29, 2020

cspotcode removed the needs more info label Dec 10, 2020

xgqfrms added a commit to web-fullstack/patch-package-in-action that referenced this issue Mar 22, 2023

fix: ts-node & lodash & esm ✅

9c9fbd1

TypeStrong/ts-node#1062 (comment) https://www.cnblogs.com/xgqfrms/p/17245062.html

This was referenced Nov 12, 2023

ts-node error on build attempt shadcn-ui/ui#1926

Closed

fix(build): replace ts-node with tsx to resolve issues with modules shadcn-ui/ui#1937

Closed

fix(build): replace ts-node with tsx to resolve issues with modules shadcn-ui/ui#1977

Merged

gordonsyme added a commit to gordonsyme/circleci-config-sdk-ts that referenced this issue Jan 16, 2024

Apparently a dependency declaring "type": "module" impacts ts-node's …

97edf8d

…ability to compile code TypeStrong/ts-node#1062 (comment)

Artim96 mentioned this issue Apr 9, 2024

systemd service file for v2.0 (was: unexpected string in JSON after upgrade to v2) ether/etherpad-lite#6306

Closed

zaporter-work mentioned this issue Nov 12, 2024

Add type: module to package.json viamrobotics/viam-typescript-sdk#413

Merged

Error: unknown file extension .ts #1062

Error: unknown file extension .ts #1062

Comments

Thomas1664 commented May 30, 2020

Expected Behavior

Actual Behavior

Steps to reproduce the problem

Minimal reproduction

Specifications

cspotcode commented Jun 2, 2020

alexcochran commented Jun 6, 2020

Aguinaldo-Alberto-Naldo commented Jun 21, 2020

cspotcode commented Jun 21, 2020 via email

clinkadink commented Jun 28, 2020

SaintPhill commented Jul 16, 2020

Thomas1664 commented Jul 16, 2020

SaintPhill commented Jul 16, 2020

Thomas1664 commented Jul 17, 2020 • edited Loading

cspotcode commented Jul 29, 2020

paxperscientiam commented Dec 10, 2020

cspotcode commented Dec 10, 2020

a-h commented Jan 26, 2021

kseebrinegar commented Feb 15, 2021

buzuosheng commented Mar 15, 2021

itcat99 commented Apr 14, 2021

Rollingegg commented Apr 14, 2021

shanoysinc commented Apr 29, 2021

Abeautifulsnow commented May 17, 2021

iway1 commented Jun 18, 2021

Mehak-Mehta commented Jun 18, 2021

Cobular commented Aug 2, 2021

goldEli commented Oct 8, 2021

iseekTo commented Oct 15, 2021

karlhorky commented Oct 22, 2021 • edited Loading

cspotcode commented Oct 22, 2021

xgqfrms commented Mar 22, 2023 • edited Loading

ts-node error ❌

ESM solution ✅

refs

leonasdev commented Apr 10, 2023

VladBrok commented Jun 1, 2023

neerajkumar161 commented Jul 2, 2023

JuYiYang commented Aug 19, 2023

88brmig commented Aug 23, 2023

JuYiYang commented Aug 24, 2023

jhonatanAlanFerreira commented Dec 7, 2023

quantuminformation commented Dec 11, 2023

arsinclair commented Dec 16, 2023

ejas404 commented Jan 7, 2024 • edited Loading

arsinclair commented Jan 8, 2024 • edited Loading

jamesrr39 commented Jan 10, 2024

Rush commented Jan 11, 2024 • edited Loading

C0D3O commented Feb 22, 2024 • edited Loading

eminoda commented Apr 12, 2024 • edited Loading

hellznrg commented Jun 4, 2024

Thomas1664 commented Jul 17, 2020 •

edited

Loading

karlhorky commented Oct 22, 2021 •

edited

Loading

xgqfrms commented Mar 22, 2023 •

edited

Loading

ejas404 commented Jan 7, 2024 •

edited

Loading

arsinclair commented Jan 8, 2024 •

edited

Loading

Rush commented Jan 11, 2024 •

edited

Loading

C0D3O commented Feb 22, 2024 •

edited

Loading

eminoda commented Apr 12, 2024 •

edited

Loading