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

https://github.com/TypeStrong/ts-node/issues/935

If you don't want to remove "type": "module" (for example if you're using import statements in your .ts which allows the inference of types from modules), then you can use the following option in tsconfig.json:

{
  "compilerOptions": {
    "esModuleInterop": true,
  }
}

And then you can start the server with the config using ts-node.

Install:

npm install -g ts-node

Run:

ts-node my_server.ts

I followed advice given herein. I also had to uninstall lodash-es and install lodash instead to make it work.

Add this to tsconfig.json

{
  /* ... your props ... */

  "ts-node": {
    "compilerOptions": {
      "module": "CommonJS"
    }
  }
}

In your package.json {Module:commonJS}, and tsconfig.json {module:commonJS},to ts-node youname.ts

Update: Thanks to some maintainers, a working solution is now officially documented by webpack. Just take a small look at the official webpack documentation.

The second solution is similar to other answers here and works perfectly fine in my case.

I changed my imports from:

import blah from './modules/blah'

to

import blah from './modules.blah.js'

Ran into this if I'm importing typescript code from a react library but for a backend script, in this case mocha tests. Its expecting .ts files but finding .tsx files I think.

In my case I had to move some functions from the .tsx react files into the .ts backend code I was working with.

I was trying to run both js and ts files on the same package with "type": "module" set using es6 syntax for imports. Following mysterycommand's answer, installing ts-node package and running ts files with node --loader ts-node/esm worked.

Solution One

1. Remove "type": "module" from package.json if it's added
2. In tsconfig.json under the compilerOptions Set module property to CommonJS module: "CommonJS" and moduleResolution: "Node"

Solution Two

if the first one didn't work, or you have for some reason to keep module: "ESNext"

1- Add "type": "module" to package.json

2- Install ts-node npm i -g ts-node

3- Go to tsconfig.json and add the following:

{
    "compilerOptions": {
        "module": "ESNext",
        "moduleResolution": "Node",
        /* ... your props ... */
    },
    "ts-node": {
        "esm": true
    }
}

4- Run ts-node fileName.ts

@2022 March

Just remove this line from packages json "type": "modules"

I got this solution after searching in google.

In order to fix this problem, you need to remove "type": "modules" from the packages.json file. Once this has been removed, your project should work.

Article link (communicode.io)

MARCH 2022

USING: Node 16.6.2, ts-node v 10.7.0

What worked for me was having "type": "module" in package.json, and adding

node --experimental-specifier-resolution=node --loader ts-node/esm ./src/app.ts

tsconfig.json:

{
    "compilerOptions": {
      "module": "ESNext",
      "esModuleInterop": true,
      "target": "ESNext",
      "moduleResolution": "Node",
      "outDir": "dist",
      "forceConsistentCasingInFileNames": true,
      "noFallthroughCasesInSwitch": true,
      "isolatedModules": false,
      "strict": true,
      "noImplicitAny": true,
      "useUnknownInCatchVariables": false,
      "inlineSourceMap": true
    },
    "ts-node": {
        "esm": true
    },
    "lib": ["esnext"]
}

Credits to @FelipePlets for the useful answer here

EDIT You may want to use a non-esnext option, as per the ts docs:

The special ESNext value refers to the highest version your version of TypeScript supports. This setting should be used with caution, since it doesn’t mean the same thing between different TypeScript versions and can make upgrades less predictable.

changing my

"moduleResolution": "node", 

to

"moduleResolution": "Node",

in package.json solved this for me

I first came across this problem probably over a year ago, and ts-node has yet to fix it. None of the above solutions worked for me, and I have seemingly tried everything.

I just resorted to using tsc --outDir out file.ts and then running the file normally with node out/file.js, and then adding out to the .gitignore.

The thought behind ts-node is wonderful, just really sucks when it can't handle seemingly straightforward examples like this. Apologies the solution doesn't use ts-node, but I couldn't get it to work.

Not sure if this will help anyone but I fixed it by putting this at the start:

#!/usr/bin/env node

Removing "type": "module" from package.json and adding:

  "compilerOptions": {
    "module": "CommonJS"
  },

In tsconfig.json fixed this for me.

use

node --loader ts-node/esm ./my-script.ts

instead of

ts-node ./my-script.ts

before this:

node --loader ts-node/esm ./my-script.ts

I had to update ssri

npm update ssri --depth 5