SyntaxError: Cannot use import statement outside a module #922

d1y · 2019-12-03T02:36:35Z

I use nextjs

import koa from 'koa'
import next from 'next'
import clear from 'clear'
import body from 'koa-bodyparser'
import cors from 'koa-cors'
import logger from 'koa-logger'
import Api from './router'
const dev = process.env.NODE_ENV !== 'production'
const App = next({ dev })
const handle = App.getRequestHandler()
const PORT = parseInt(process.env.NODE_PORT) || 3000

App.prepare().then(() => {
  const Server = new koa()

  Server.use(body())
  Server.use(cors())
  Server.use(logger())

  Server
    .use(Api.routes())
    .use(Api.allowedMethods())

  Server.use(async ctx=> {
    // https://thecodebarbarian.com/building-a-nextjs-app-with-mongodb
    await handle(ctx.req, ctx.res)
    ctx.respond = false
  })

  Server.listen(PORT, () => {
    clear()
    const cowsay = require('cowsay-browser')
    const text = `Koa server listen in ${ PORT }`
    console.log(cowsay.say({ text }))
  })

})

use ts-node server.ts, BTW

➜  next git:(dev) ✗ ts-node server.ts 
/home/d1y/cat/coface/code/next/server.ts:10
import koa from 'koa';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Module._compile (internal/modules/cjs/loader.js:892:18)
    at Module.m._compile (/usr/node/node-v12.13.0-linux-x64/lib/node_modules/ts-node/src/index.ts:536:23)
    at Module._extensions..js (internal/modules/cjs/loader.js:973:10)
    at Object.require.extensions.<computed> [as .ts] (/usr/node/node-v12.13.0-linux-x64/lib/node_modules/ts-node/src/index.ts:539:12)
    at Module.load (internal/modules/cjs/loader.js:812:32)
    at Function.Module._load (internal/modules/cjs/loader.js:724:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
    at main (/usr/node/node-v12.13.0-linux-x64/lib/node_modules/ts-node/src/bin.ts:212:14)
    at Object.<anonymous> (/usr/node/node-v12.13.0-linux-x64/lib/node_modules/ts-node/src/bin.ts:470:3)
    at Module._compile (internal/modules/cjs/loader.js:956:30)

my tsconfig.json file

{
  "compilerOptions": {
    "target": "es6",
    "lib": [
      "es6"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": false,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "es2015",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "noImplicitAny": true
  },
  "exclude": [
    "node_modules"
  ],
  "include": [
    "next-env.d.ts",
    "**/*.ts",
    "**/*.tsx"
  ]
}

Why is this?

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

d1y · 2019-12-03T02:39:48Z

@blakeembrey

blakeembrey · 2019-12-03T02:46:03Z

You’re trying to execute use it as an ES2015 module, but node.js currently understands CommonJS.

blakeembrey · 2019-12-03T03:20:41Z

Added documentation: https://github.com/TypeStrong/ts-node#syntaxerror.

xeruf · 2020-01-07T14:40:31Z

Having the same problem even when using commonjs

	"compilerOptions": {
		/* Basic Options */
		"target": "es2016",
		/* Specify ECMAScript target version: 'ES3' (default),	'ES5',	'ES2015',	'ES2016',	'ES2017',	'ES2018' or 'ESNEXT'. */
		"module": "commonjs",

My project is an expo react-native project, but that shouldn't make a difference.

But the error does seem to come from a dependency:

.../node_modules/expo-constants/build/Constants.js:1
import { AppOwnership, UserInterfaceIdiom, } from './Constants.types';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Module._compile (internal/modules/cjs/loader.js:895:18)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Module.require (internal/modules/cjs/loader.js:852:19)
    at require (internal/modules/cjs/helpers.js:74:18)

Nditah · 2020-01-07T19:28:45Z

Update 3: Since Node 13, you can use either the .mjs extension or set "type": "module" in your package.json. You don't need to use the --experimental-modules flag.

Update 2: Since Node 12, you can use either the .mjs extension or set "type": "module" in your package.json. And you need to run node with the --experimental-modules flag.

Update: In Node 9, it is enabled behind a flag, and uses the .mjs extension.

node --experimental-modules my-app.mjs

https://stackoverflow.com/questions/39436322/node-js-syntaxerror-unexpected-token-import?rq=1

xeruf · 2020-01-09T18:40:34Z

Thanks, I got it fixed that way!

icemars123 · 2020-02-13T01:43:14Z

I had the same problem when I started to used babel... But later, I had a solution... I haven't had the problem anymore so far... Currently, Node v12.14.1, "@babel/node": "^7.8.4", I use babel-node and nodemon to execute (node is fine as well..)

package.json:
"start": "nodemon --exec babel-node server.js
"debug": "babel-node debug server.js" !!note: server.js is my entry file, you can use yours.

launch.json:
When you debug, you also need to config your launch.json file
"runtimeExecutable": "${workspaceRoot}/node_modules/.bin/babel-node"

Of course, with babel-node, you also normally need and edit another file, such as babel.config.js/.babelrc file

dimahali · 2020-03-03T18:23:35Z

I had the same problem and somehow fixed it. I have written a post about this, hope this helps https://xperimentalhamid.com/how-do-i/fix-cannot-use-import-statement-outside-a-module/

mfahad24 · 2020-03-19T17:09:35Z

I had the same problem and somehow fixed it. I have written a post about this, hope this helps https://xperimentalhamid.com/how-do-i/fix-cannot-use-import-statement-outside-a-module/

.mjs extension worked for me, thank you!!

haouarihk · 2020-03-24T20:51:31Z

i keep getting this error when i import react in node for some reason
in my project
``
import React from 'react'
^^^^^^

SyntaxError: Cannot use import statement outside a module
``

kaiyuan0708 · 2020-04-02T06:50:21Z

Do u solve this?

htolajide · 2020-04-13T16:16:07Z

If its an express project make this the last line in your server.js or app.js file
module.exports = app;
where app is from declared earlier, this this can be any valid variable but here app is used.
const app = express();

nxpatterns · 2020-04-14T20:23:11Z

To load an ES module, set "type": "module" in the package.json or use the .mjs extension.

davidwoodward · 2020-04-18T22:05:31Z

"type": "module" works, but only works if you are using Node v13.9.0 or above.

fuadnafiz98 · 2020-04-30T16:25:16Z

Add .babelrc to root folder

~/.babelrc

{
  "presets": ["env", "stage-0"]
}

my package.json

~/package.json

"scripts": {
    "watch": "nodemon --exec babel-node src/index.js"
  },
  "dependencies": {
    "dotenv": "^8.2.0",
  },
  "devDependencies": {
    "babel-cli": "^6.26.0",
    "babel-preset-env": "^1.7.0",
    "babel-preset-stage-0": "^6.24.1",
    "nodemon": "^2.0.3"
  }

tokland · 2020-07-31T11:35:50Z

When using a tsconfig.json, you may override just the module setting like this:

$ npx ts-node -O '{"module":"commonjs"}' my-script.ts

Dravere · 2020-08-12T23:00:56Z

In case you stumble upon this and don't want to change the module option to commonjs because this will mess with your tree shaking in webpack. You can have more than one tsconfig.json. ts-loader supports a config entry named configFile. There is also a possibility for extending tsconfig.json files.

In my case I had a vue project and I wanted to test some parts of it with mocha/chai. I created a tsconfig.base.json with the common options. The tsconfig.json file extends the base file and is setup to run with mocha. It's module setting is set to commonjs. Additionally I created a tsconfig.webpack.json extending the base file that has its module config set to es2015 that is provided to configFile in the ts-loader options. I changed no other options anywhere else, so no type: "module" in package.json that was mentioned in this issue since this would interfere with webpack 4.x.

Also as additional info ts-node supports providing a different tsconfig.json via the -P or --project command line option.

cspotcode · 2020-08-12T23:14:56Z

@Dravere we also support overriding compilerOptions inside the same tsconfig, which will only apply to ts-node. So you can keep it all in a single tsconfig file if you want.

{
  "ts-node": {
    // these options are overrides used only by ts-node
    // same as our --compilerOptions flag and our TS_NODE_COMPILER_OPTIONS environment variable
    "compilerOptions": {
      "module": "commonjs"
    }
  },
  "compilerOptions": {
    "module": "esnext"
  }

Dravere · 2020-08-12T23:23:10Z

@cspotcode Oh, that is amazing. Thanks for that hint. Learned a lot about Typescript and ts-node while trying to fix that problem.

* This was required to run ava tests as .ts file - Fixes "SyntaxError: Cannot use import statement outside a module" * Found this as work around noted here - TypeStrong/ts-node#922 (comment)

iltonbarbosa · 2021-03-22T22:27:12Z

I have the same problem

iltonbarbosa · 2021-03-23T23:28:33Z

I am experiencing this error when using a postinstall script in a node_module, I am under the impression that maybe ts-node call in package.json of node_module is picking up the tsconfig.json of the parent rather than it's local one?

The parent repo has module: es2020 in config because it is an AngularJS project, whereas the child is just a pure CommonJS style project.

Estou com este mesmo problema no nodejs. Alguém pode me ajudar, por favor?

* This was required to run ava tests as .ts file - Fixes "SyntaxError: Cannot use import statement outside a module" * Found this as work around noted here - TypeStrong/ts-node#922 (comment)

acomito · 2021-07-26T13:42:18Z

I get

Unknown compiler option 'ts-node'

When I try this

{
  "compilerOptions": {
    "module": "esnext",
    "moduleResolution": "node",
    "target": "es2017",
    "outDir": "./dist",
    "lib": ["es6"],
    "types": ["node", "graphql", "express"],
    "typeRoots": ["./node_modules/@types", "./src/@types"],
    "experimentalDecorators": true,
    "allowSyntheticDefaultImports": true,
    "emitDecoratorMetadata": true,
    "resolveJsonModule": true,
    "pretty": true,
    "sourceMap": true,
    "esModuleInterop": true,
    "isolatedModules": true,
    "allowJs": true,
    "ts-node": {
      "compilerOptions": {
        "module": "commonjs"
      }
    },
  },
  "include": ["src/entities/**/*.ts", "src/**/*.ts", "src/**/*.js", "./index.ts"],
  "exclude": ["node_modules","ormlogs.log", "dist"]
}

fspoettel · 2021-07-26T17:11:59Z

@acomito the ts-node key needs to be set on the top-level, not nested in compilerOptions.

TypeStrong/ts-node#922

RahulChouhan96 · 2021-09-04T10:18:36Z

Update 3: Since Node 13, you can use either the .mjs extension or set "type": "module" in your package.json. You don't need to use the --experimental-modules flag.

Update 2: Since Node 12, you can use either the .mjs extension or set "type": "module" in your package.json. And you need to run node with the --experimental-modules flag.

Update: In Node 9, it is enabled behind a flag, and uses the .mjs extension.

node --experimental-modules my-app.mjs

https://stackoverflow.com/questions/39436322/node-js-syntaxerror-unexpected-token-import?rq=1

How am I supposed to use mjs extension for the ts file? There is typescript-specific code present (like setting type) which is not possible in mjs or in any other file type.

For eg. I got these two errors
SyntaxError: Unexpected token ':' and
Type annotations can only be used in TypeScript files.ts(8010)
in this code, when I changed extension form ts to mjs

function run(): void {   // <------- Colon (:) is causing SyntaxError: Unexpected token ':' and
                         //          void is causing error Type annotations can only be used in TypeScript files.ts(8010)
      // Some code
}

@Nditah

xiaoshude · 2021-09-06T05:50:40Z

@Dravere we also support overriding compilerOptions inside the same tsconfig, which will only apply to ts-node. So you can keep it all in a single tsconfig file if you want.
{
  "ts-node": {
    // these options are overrides used only by ts-node
    // same as our --compilerOptions flag and our TS_NODE_COMPILER_OPTIONS environment variable
    "compilerOptions": {
      "module": "commonjs"
    }
  },
  "compilerOptions": {
    "module": "esnext"
  }

this works! thanks a lot!

quizdeveloper · 2021-11-20T10:09:39Z

I got the same error because I have imported a lib with syntax import ... from and after I change to require() that bug is solved for me. You can see more detail here

TypeStrong/ts-node#922 (comment)

ialiaslani · 2021-12-18T06:12:47Z

i got the same error because I forgot to set extname in file that I was Importing

leonheess · 2022-05-06T21:21:53Z

What if I can't go back to module: 'commonjs'?

https://stackoverflow.com/questions/72147353/how-to-use-normal-imports-and-top-level-await-at-the-same-time

eden-lane · 2022-12-11T09:37:16Z

@Dravere we also support overriding compilerOptions inside the same tsconfig, which will only apply to ts-node. So you can keep it all in a single tsconfig file if you want.

when I do this, I get error:

Top-level 'await' expressions are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', 'node16', or 'nodenext', and the 'target' option is set to 'es2017' or higher.

airtonix · 2023-04-24T05:08:57Z

This is pretty hilarious:

😸 hey bro, we got this tool that lets you run typescript on the cli!!!

🧑‍💻 Amazeballs! proceeds to type standard typescript with imports in a .ts file

💻 Error you are fail, re-evaluate life choices

🧑‍💻 🕸️ OMG QQ WTFBBQ, what is this error: ....

lib author: ./wontfix

Other Rando on the internet commenting on a typescript tool: hey lol use .mjs 👍🏻 👍🏻 👍🏻 👍🏻

🧑‍💻 ._. dude, this is typescript.

Yet Another Rando on the internet commenting on a typescript tool: hey lol add a .babelrc lmao 👍🏻 👍🏻 👍🏻 👍🏻

🧑‍💻 ./leavesbuilding

blakeembrey closed this as completed Dec 3, 2019

blakeembrey added the wontfix label Dec 3, 2019

haishengwu-okta mentioned this issue Feb 6, 2020

Enhance the email verification pages okta/okta-signin-widget#1029

Merged

Nephera mentioned this issue Feb 28, 2020

Av9 AWS Lightsail Deployment: "Error: Cannot find module /home/bitnami/projectName/node_modules/zone.js/dist/zone-node" angular/universal#1528

Closed

15 tasks

ashbrener mentioned this issue Mar 15, 2020

SyntaxError: Unexpected token 'export' abdoolly/ts-node-builder#1

Open

LouisSung mentioned this issue Mar 26, 2020

About debug NestJS in Nx using WebStorm nrwl/nx#2701

Closed

4 tasks

alex-ketch mentioned this issue Apr 21, 2020

feat(Build): Create & publish modern JS builds stencila/executa#121

Merged

2 tasks

anselmoshim mentioned this issue May 4, 2020

npm run build fails on a brand new project ant-design/ant-design-pro#6523

Closed

B4nan mentioned this issue Jun 8, 2020

MikroORM + Angular + Electron SyntaxError: Cannot use import statement outside a module mikro-orm/mikro-orm#604

Closed

sihil mentioned this issue Aug 25, 2020

New methods file faithege/aws-basics-practice#5

Open

TalTamir86 mentioned this issue Sep 1, 2020

Querying firestore data to produce the heatmap and refactoring googleinterns/ellipsis-step-internship#6

Merged

voorjaar mentioned this issue Mar 19, 2021

Cannot use import statement outside a module unjs/jiti#25

Closed

quadratz mentioned this issue Jul 12, 2021

ES Module error: Cannot use import statement outside a module wclr/ts-node-dev#265

Open

barticus mentioned this issue Aug 19, 2021

Having trouble using with ts-node/ts-node-dev ShogunPanda/fastify-openapi-docs#3

Closed

Dan503 mentioned this issue Aug 25, 2021

Typescript support is broken gulpjs/gulp#2623

Closed

linonetwo added a commit to tiddly-gittly/TidGi-Desktop that referenced this issue Aug 25, 2021

fix: ts-node Cannot use import statement outside a module

ae349cc

TypeStrong/ts-node#922

codyebberson mentioned this issue Sep 13, 2021

ES Modules medplum/medplum#83

Closed

DevenWen pushed a commit to DevenWen/phaser3-typescript-parcel-template that referenced this issue Nov 21, 2021

add unit test;

82af8e6

TypeStrong/ts-node#922 (comment)

Cansiny0320 mentioned this issue Dec 31, 2021

使用 ts-node 时报错 Cannot use import statement outside a module Cansiny0320/issues#6

Open

avi12 mentioned this issue Jan 28, 2022

Cannot use the example from the README fregante/chrome-webstore-upload#57

Closed

SlyPuffin mentioned this issue Feb 15, 2022

Main Screen & Review w/ Dummy Cards SlyPuffin/gyrifier-app#2

Merged

mytharcher mentioned this issue Jun 6, 2022

chore(debug): add debug config nocobase/nocobase#475

Merged

This was referenced Aug 26, 2022

Getting "Cannot use import statement outside a module" #1872

Closed

Package's main script not treated as module depending if it's file-system local or not #1876

Closed

francescov1 mentioned this issue Mar 31, 2024

ESM Support francescov1/mongoose-tsgen#139

Closed

stassribnyi mentioned this issue May 3, 2024

Feat/update icons compile script to support icon deprecation rentalutions/elements#264

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SyntaxError: Cannot use import statement outside a module #922

SyntaxError: Cannot use import statement outside a module #922

d1y commented Dec 3, 2019

d1y commented Dec 3, 2019

blakeembrey commented Dec 3, 2019 •

edited

Loading

blakeembrey commented Dec 3, 2019

xeruf commented Jan 7, 2020

Nditah commented Jan 7, 2020

xeruf commented Jan 9, 2020

icemars123 commented Feb 13, 2020

dimahali commented Mar 3, 2020

mfahad24 commented Mar 19, 2020

haouarihk commented Mar 24, 2020

kaiyuan0708 commented Apr 2, 2020

htolajide commented Apr 13, 2020

nxpatterns commented Apr 14, 2020

davidwoodward commented Apr 18, 2020

fuadnafiz98 commented Apr 30, 2020

tokland commented Jul 31, 2020 •

edited

Loading

Dravere commented Aug 12, 2020

cspotcode commented Aug 12, 2020

Dravere commented Aug 12, 2020

iltonbarbosa commented Mar 22, 2021

iltonbarbosa commented Mar 23, 2021

acomito commented Jul 26, 2021 •

edited

Loading

fspoettel commented Jul 26, 2021

RahulChouhan96 commented Sep 4, 2021 •

edited

Loading

xiaoshude commented Sep 6, 2021

quizdeveloper commented Nov 20, 2021

ialiaslani commented Dec 18, 2021

leonheess commented May 6, 2022

eden-lane commented Dec 11, 2022

airtonix commented Apr 24, 2023 •

edited

Loading

SyntaxError: Cannot use import statement outside a module #922

SyntaxError: Cannot use import statement outside a module #922

Comments

d1y commented Dec 3, 2019

d1y commented Dec 3, 2019

blakeembrey commented Dec 3, 2019 • edited Loading

blakeembrey commented Dec 3, 2019

xeruf commented Jan 7, 2020

Nditah commented Jan 7, 2020

xeruf commented Jan 9, 2020

icemars123 commented Feb 13, 2020

dimahali commented Mar 3, 2020

mfahad24 commented Mar 19, 2020

haouarihk commented Mar 24, 2020

kaiyuan0708 commented Apr 2, 2020

htolajide commented Apr 13, 2020

nxpatterns commented Apr 14, 2020

davidwoodward commented Apr 18, 2020

fuadnafiz98 commented Apr 30, 2020

Add .babelrc to root folder

my package.json

tokland commented Jul 31, 2020 • edited Loading

Dravere commented Aug 12, 2020

cspotcode commented Aug 12, 2020

Dravere commented Aug 12, 2020

iltonbarbosa commented Mar 22, 2021

iltonbarbosa commented Mar 23, 2021

acomito commented Jul 26, 2021 • edited Loading

fspoettel commented Jul 26, 2021

RahulChouhan96 commented Sep 4, 2021 • edited Loading

xiaoshude commented Sep 6, 2021

quizdeveloper commented Nov 20, 2021

ialiaslani commented Dec 18, 2021

leonheess commented May 6, 2022

eden-lane commented Dec 11, 2022

airtonix commented Apr 24, 2023 • edited Loading

blakeembrey commented Dec 3, 2019 •

edited

Loading

tokland commented Jul 31, 2020 •

edited

Loading

acomito commented Jul 26, 2021 •

edited

Loading

RahulChouhan96 commented Sep 4, 2021 •

edited

Loading

airtonix commented Apr 24, 2023 •

edited

Loading