TypeError: Unknown file extension ".ts" - esmodules support #70

AuroraLantean · 2022-01-12T09:54:26Z

Original post in Anchor repo: [(https://github.com/coral-xyz/anchor/issues/1286)]

Anchor.toml [script] command:
test = "yarn run ts-mocha -p ./tsconfig.json -t 1000000 tests/**/*.ts"

The problem is the m1.ts file cannot import functions from another ts file!!!???
in my utils.ts

export const log1 = console.log;

in my m1.ts file:

import { log1 } from './utils';
describe('scenario1', async () => {
  it('initialize', async () => {
    log1('\n---------== init');
  });
});

the imported log1 function or any other function will cause the Unknown file extension ".ts" error!!??

my local package dependencies:
"mocha": "^9.1.3",
"ts-mocha": "^9.0.0-alpha1",
"ts-node": "^10.4.0",
"typescript": "^4.5.4"

Please advise. Thank you

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

piotrwitek · 2022-01-12T15:03:18Z

please test with new v9.0.0
9.0.0-alpha1 is experimental

AuroraLantean · 2022-01-13T03:52:22Z

Thank you for your post... but "ts-mocha": "9.0.0" results in the same error as above.

piotrwitek · 2022-01-13T16:06:38Z

@AuroraLantean need a little bit of help, if you could help me to create a simple repo with your setup (package.json and m1.ts + utils.ts files and npm test command) I would try to investigate that repo and fix that issue and also look for a way to add it to the regression testing for your use-case.

I guess it's related to the ts-node version, not sure why you have installed it in your project but it's different from ts-mocha version possibly clashing.

AuroraLantean · 2022-01-14T11:15:45Z

Hi @piotrwitek , thank you for your quick reply. Please take the following code:
https://github.com/AuroraLantean/SolanaAnchorDemo2
Thank you!

Burwin · 2022-01-20T18:04:25Z

For another example, I was able to reproduce it with the following repo after installing/using dateformat: https://github.com/Burwin/ts-mocha-file-extension

simonbuchan · 2022-02-02T05:05:24Z

Pretty sure this is due to type: module in package.json (possibly in a dep). See the ts-node issue for this.

Not sure how to mangle ts-mocha into doing the right thing here? Something like node --loader=ts-node/esm ts-mocha ... should be enough, but doesn't work for me, perhaps ts-mocha needs to support --loader itself?

cn-ia · 2022-02-20T14:17:21Z

Try ts-mocha -n loader=ts-node/esm -p tsconfig.json tests/**/*.test.ts via npm scripts, it works for me!
(Optional) Check npx ts-mocha --help for more details of this option.

DoodahProductions · 2022-03-01T22:27:43Z

Hello, having the same issue here. Trying @cn-ia solution did not work for me

DoodahProductions · 2022-03-01T23:44:42Z

If that can help, I found out that this issue seems to be triggered when I do use the package get-port version >= ^6.0.0
If I do remove this package, tests are running correctly. If I add this package, then my test command produce the error TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"

Test command :

"test": "ts-mocha -p tsconfig.json 'test/**/*.ts'",

TsConfig:

{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6",
    "composite": true,
    "outDir": "dist",
    "rootDir": ".",
    "sourceMap": true,
    "strict": false,
    "declaration": true,
    "esModuleInterop": true,
    "resolveJsonModule": true
  },
  "include": [
    "./**/*.ts",
    "src/definitions/**/*.json",
    "src/modules/tasks"
  ],
  "exclude": [
    "node_modules",
    "dist",
    "test"
  ]
}

sagrawal31 · 2022-05-05T08:32:13Z

Pretty sure this is due to type: module in package.json (possibly in a dep). See the ts-node issue for this.

Not sure how to mangle ts-mocha into doing the right thing here? Something like node --loader=ts-node/esm ts-mocha ... should be enough, but doesn't work for me, perhaps ts-mocha needs to support --loader itself?

For me, this was the problem. Removing "type": "module" from package.json fixed the problem for me.

SmashingQuasar · 2022-05-18T17:58:40Z

Hey! I have the same issue. I do not have "type": "module" in my package.json so it might be something else. Honestly my package.json is extremely simple so it's doubtful that it originates from there. I'm using ts-mocha version 10.0.0 and ts-node version 10.7.0.

felipeplets · 2022-06-05T19:15:02Z

@SmashingQuasar I believe the issue is because ts-mocha depends on 1ts-node@7.0.11 which didn't support ESM it would need to depend on 10+ or to have it as a peer dependency although that would force all developers to install ts-node themselves even if they don't use ts-node for other reasons.

If you run npm ls ts-node in your project you should see something like:

@my-project@ /Users/myuser/projects/my-project
├─┬ ts-mocha@10.0.0
│ └── ts-node@7.0.1
└── ts-node@10.7.0

Showing that although your project uses a newer ts-node version ts-mocha still uses an older version.

piotrwitek · 2022-06-09T11:10:37Z

Hello Everyone, thanks for multiple useful contributions here in this issue, I'll try to look into this issue today and propose some solutions, also I will try to include a special test case scenario on a branch in the repo to help with debugging. Cheers!

piotrwitek · 2022-06-09T14:51:18Z

I have created a branch with a reproduction test case for experimentation here: https://github.com/piotrwitek/ts-mocha/tree/support-for-node-es-modules

After some research, the issue was indeed introduced by ts-node dependency not handling esmodules and I found some solutions we could try to implement:

mocha and native ESM TypeStrong/ts-node#1268

More details on ts-node esm support:

I won't have time to work on it anytime soon, but will try to help and accept PRs for this. Cheers!

cspotcode · 2022-06-21T22:07:00Z

Let me know if you need guidance on the best way to use our ESM loader.

fiftin · 2022-07-05T17:48:09Z

Same issue.

yasinkocak · 2022-07-14T13:38:31Z

Same issue

hebelal · 2022-07-29T09:35:53Z

same issue

gliese1337 · 2022-08-16T23:33:22Z

Just ran into the same issue myself.

manooog · 2022-08-17T01:51:50Z

Hello everyone,I have the same problem and I think the problem was caused by tsconfig.json：

// ❌ when module = esnext
{
	"compilerOptions": {
    	"module": "esnext"
    }
}
// ✅ change module to commonjs,then everything is ok
{
	"compilerOptions": {
    	"module": "CommonJS"
    }
}

Hope this trick can help.

janholusa · 2022-09-22T07:35:59Z

I got the same issue with
package.json:

"scripts": 
    "test": "mocha --require ts-node/register test/**/*_spec.ts",
},
"devDependencies": {    
      "@types/chai": "^4.3.3",
      "@types/mocha": "^9.1.1",
      "chai": "^4.3.6",
      "mocha": "^10.0.0",
      "ts-mock-imports": "^1.3.8",
      "ts-node": "^10.9.1",
      "typescript": "^4.8.3"
}

attempt to run test npm run test throws this:

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /somepath/test/binding/cookieNumArray_spec.ts
    at new NodeError (node:internal/errors:372:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:80:11)
    at defaultGetFormat (node:internal/modules/esm/get_format:122:38)
    at defaultLoad (node:internal/modules/esm/load:21:20)
    at ESMLoader.load (node:internal/modules/esm/loader:431:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:350:22)
    at new ModuleJob (node:internal/modules/esm/module_job:66:26)
    at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:369:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:328:34)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:409:24)
    at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)
    at async formattedImport (/somepath/node_modules/mocha/lib/nodejs/esm-utils.js:7:14)
    at async Object.exports.requireOrImport (/somepath/node_modules/mocha/lib/nodejs/esm-utils.js:38:28)
    at async Object.exports.loadFilesAsync (/somepath/node_modules/mocha/lib/nodejs/esm-utils.js:91:20)
    at async singleRun (/somepath/node_modules/mocha/lib/cli/run-helpers.js:125:3)
    at async Object.exports.handler (/somepath/node_modules/mocha/lib/cli/run.js:370:5)

piotrwitek · 2022-09-22T11:14:39Z

seems like a problem with Node itself, if someone can make a working example using mocha and ts-node I would be able to integrate it into the library

cspotcode · 2022-09-22T14:08:46Z

Needs the --loader flag, due to node limitations. Node does not allow programmatic API nor --require to hook ESM.

piotrwitek · 2022-09-22T16:53:48Z

@cspotcode thanks for jumping in and correcting my assumptions! Could you point me to some examples or solutions that are using mocha and ts-node with ESM successfully that I could try?

cspotcode · 2022-09-22T16:58:26Z

Google found this: TypeStrong/ts-node#1268

h-unterp · 2022-10-04T21:31:40Z

create .mocharc.json and

{ 
    "node-option": [
	 "loader=ts-node/esm"
     ]
}

Windovvsill · 2022-10-17T17:29:43Z

In my case, on of my dependencies (nanoid) added "type": "module" to their package.json. I had to downgrade nanoid to fix mocha.

nmklotas · 2023-02-04T18:41:31Z

Nanoid got me too

Polve · 2023-03-01T10:41:36Z

same problem here, and I need to use type: module

The tsconfig.json contents taken from piotrwitek/ts-mocha#70 (comment)

quantuminformation · 2023-04-22T11:22:19Z

came across this today

"ts-mocha": "^10.0.0"

➜  fireproof git:(main) ✗ pnpm test

> @fireproof/core@0.5.6 test /Users/nikos/WebstormProjects/fireproof-nikos-clone/packages/fireproof
> npm run test:mocha


> @fireproof/core@0.5.6 test:mocha
> ts-mocha test/*.test.ts


TypeError: Unknown file extension ".ts" for /Users/nikos/WebstormProjects/fireproof-nikos-clone/packages/fireproof/test/clock.test.ts
    at new NodeError (node:internal/errors:399:5)
    at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:79:11)
    at defaultGetFormat (node:internal/modules/esm/get_format:121:38)
    at defaultLoad (node:internal/modules/esm/load:81:20)
    at nextLoad (node:internal/modules/esm/loader:163:28)
    at ESMLoader.load (node:internal/modules/esm/loader:605:26)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:457:22)
    at new ModuleJob (node:internal/modules/esm/module_job:64:26)
    at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:480:17)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:434:34)```

![Uploading image.png…]()

matthew-dean · 2023-05-01T21:56:14Z

I've tried a variety of solutions in this thread. These did not work:

Changing tsconfig.json's module type to commonjs was not a fix. (This was already the case.)
Changing "type": "module" in package.json was not a fix. (Wasn't the case.)
Adding loader=ts-node/esm did not fix things.
Changing mocha / ts-mocha / ts-node versions did not fix things.

So, I'm kind of at a loss.

quantuminformation · 2023-05-02T20:53:24Z

i switched to vitest, almost there

webJose · 2023-08-05T07:34:42Z

Like others, I suffer from this same pain. I have tried all solutions to no avail. If anyone has any updated information, please share.

Thanks.

Polve · 2023-08-05T07:51:53Z

hoping this can help somebody: I was able to make it work creating a .mocharc.json file with this content:

{
    "node-option": [
        "loader=ts-node/esm"
    ]
}

tim-rohrer · 2023-09-08T22:22:00Z

create .mocharc.json and

{ 
    "node-option": [
	 "loader=ts-node/esm"
     ]
}

I tried adding this but then get:

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/<path-to-project>/node_modules/ts-node/esm' imported from /<path-to-project>/
    at new NodeError (node:internal/errors:405:5)
    at finalizeResolution (node:internal/modules/esm/resolve:324:11)
    at moduleResolve (node:internal/modules/esm/resolve:943:10)
    at defaultResolve (node:internal/modules/esm/resolve:1129:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ESMLoader.import (node:internal/modules/esm/loader:524:22)
    at initializeLoader (node:internal/process/esm_loader:75:58)
    at loadESM (node:internal/process/esm_loader:90:11) {
  code: 'ERR_MODULE_NOT_FOUND'
}

node 18.17.0

cn-ia · 2023-09-08T22:33:34Z

create .mocharc.json and

{ 
    "node-option": [
	 "loader=ts-node/esm"
     ]
}

I tried adding this but then get:

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/<path-to-project>/node_modules/ts-node/esm' imported from /<path-to-project>/
    at new NodeError (node:internal/errors:405:5)
    at finalizeResolution (node:internal/modules/esm/resolve:324:11)
    at moduleResolve (node:internal/modules/esm/resolve:943:10)
    at defaultResolve (node:internal/modules/esm/resolve:1129:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ESMLoader.import (node:internal/modules/esm/loader:524:22)
    at initializeLoader (node:internal/process/esm_loader:75:58)
    at loadESM (node:internal/process/esm_loader:90:11) {
  code: 'ERR_MODULE_NOT_FOUND'
}

node 18.17.0

Do you have dependency ts-node in your project dependencies tree (package.json) ? Install it and try again.

tim-rohrer · 2023-09-08T22:35:32Z

Ha! I hadn't checked, assuming it was installed as a dep of ts-mocha.

Actually, I got the steps here to work without ts-mocha.

Thank you though.

matthew-dean · 2023-09-13T17:36:18Z

@webJose So, since I commented on this, I've switched test runners to Vitest in every scenario. As far as I can tell, Jest / Mocha just don't work, or don't work consistently, and Vitest works with very little configuration.

Akronae · 2024-03-23T08:05:43Z

@matthew-dean this is an order of magnitude much better. It just works, no config needed, and the API is really nice, default typescript support, no crap @types to import. If you're lucky enough to have the ability to switch please consider Vitest!

piotrwitek self-assigned this Jun 9, 2022

piotrwitek added bug enhancement help wanted labels Jun 9, 2022

piotrwitek changed the title ~~TypeError: Unknown file extension ".ts"~~ TypeError: Unknown file extension ".ts" - esmodules support Jun 9, 2022

stoically mentioned this issue Jun 24, 2022

Bumping dependencies stoically/temporary-containers#587

Open

3 tasks

bennorth added a commit to pytchlang/pytch-webapp that referenced this issue Mar 6, 2023

Add packages for mocha/typescript testing

9e11b7f

The tsconfig.json contents taken from piotrwitek/ts-mocha#70 (comment)

SimonFischer04 mentioned this issue May 14, 2023

Update dependencies / convert to ES-Modules nodecg/generator-nodecg#78

Closed

davidkhala mentioned this issue Aug 19, 2023

ts-mocha blockage to use davidkhala/ts-template#1

Open

acheroncrypto mentioned this issue Dec 6, 2023

TypeError: Unknown file extension ".ts" coral-xyz/anchor#1286

Closed

TypeError: Unknown file extension ".ts" - esmodules support #70

TypeError: Unknown file extension ".ts" - esmodules support #70

Comments

AuroraLantean commented Jan 12, 2022 • edited

piotrwitek commented Jan 12, 2022 • edited

AuroraLantean commented Jan 13, 2022

piotrwitek commented Jan 13, 2022 • edited

AuroraLantean commented Jan 14, 2022

Burwin commented Jan 20, 2022

simonbuchan commented Feb 2, 2022

cn-ia commented Feb 20, 2022

DoodahProductions commented Mar 1, 2022

DoodahProductions commented Mar 1, 2022 • edited

sagrawal31 commented May 5, 2022

SmashingQuasar commented May 18, 2022

felipeplets commented Jun 5, 2022 • edited

piotrwitek commented Jun 9, 2022

piotrwitek commented Jun 9, 2022

cspotcode commented Jun 21, 2022

fiftin commented Jul 5, 2022

yasinkocak commented Jul 14, 2022

hebelal commented Jul 29, 2022

gliese1337 commented Aug 16, 2022

manooog commented Aug 17, 2022

janholusa commented Sep 22, 2022

piotrwitek commented Sep 22, 2022 • edited

cspotcode commented Sep 22, 2022

piotrwitek commented Sep 22, 2022 • edited

cspotcode commented Sep 22, 2022

h-unterp commented Oct 4, 2022 • edited

Windovvsill commented Oct 17, 2022

nmklotas commented Feb 4, 2023

Polve commented Mar 1, 2023

quantuminformation commented Apr 22, 2023 • edited

matthew-dean commented May 1, 2023

quantuminformation commented May 2, 2023

webJose commented Aug 5, 2023

Polve commented Aug 5, 2023

tim-rohrer commented Sep 8, 2023

cn-ia commented Sep 8, 2023

tim-rohrer commented Sep 8, 2023

matthew-dean commented Sep 13, 2023

Akronae commented Mar 23, 2024

AuroraLantean commented Jan 12, 2022 •

edited

piotrwitek commented Jan 12, 2022 •

edited

piotrwitek commented Jan 13, 2022 •

edited

DoodahProductions commented Mar 1, 2022 •

edited

felipeplets commented Jun 5, 2022 •

edited

piotrwitek commented Sep 22, 2022 •

edited

piotrwitek commented Sep 22, 2022 •

edited

h-unterp commented Oct 4, 2022 •

edited

quantuminformation commented Apr 22, 2023 •

edited