Repository navigation
Add common ESM errors to Troubleshooting page #1607
Description
Activity
Note the
ERR_UNKNOWN_FILE_EXTENSIONalso happens with extensionless files, likerequire.resolve("mocha/bin/mocha")(which breaksts-mochaat the moment).Regarding
ERR_UNKNOWN_FILE_EXTENSIONand mocha's extensionless entrypoint:
Linking to https://github.com/nodejs/node/discussions/41711 where the solution is being discussed. Once a solution is settled upon, ts-node can implement a workaround to mimic the fixed behavior on old node versions.- added a commit that references this issue
on Mar 7, 2022 - added a commit that references this issue
on May 30, 2022
There are a few errors thrown by node -- and by our copy-pasted node code -- that confuse users. Add these to the troubleshooting page.
For example, when you try to
require()a TS file and it's supposed to be executed as native ESM, the user gets a crypticERR_REQUIRE_ESM. When they try to do the same viaimport()instead ofrequire()-- ornode ./index.tsinside atype: moduledirectory -- they getERR_UNKNOWN_FILE_EXTENSION