ignore eslint error: 'import' and 'export' may only appear at the top level

Question

Is it possible to deactivate this error in eslint?

Parsing error: 'import' and 'export' may only appear at the top level

This is looking like a won't fix scenario. See https://github.com/eslint/eslint/issues/2259 and also https://github.com/eslint/espree/issues/124 ; particularly, the quote from the dev at the end of 124, saying he basically sees no reason to support invalid syntax. — Paul, Aug 26 '16 at 05:08
See also:[Why must import / export declarations be top level in es2015?](http://stackoverflow.com/questions/34203325/why-must-export-import-declarations-be-on-top-level-in-es2015) — Paul, Aug 26 '16 at 05:11

Gyandeep · Accepted Answer · 2016-08-27T15:54:21.830

89

ESLint natively doesnt support this because this is against the spec. But if you use babel-eslint parser then inside your eslint config file you can do this:

{
  "parser": "babel-eslint",
  "parserOptions": {
    "sourceType": "module",
    "allowImportExportEverywhere": true
  }
}

Doc ref: https://github.com/babel/babel-eslint#configuration

edited Aug 27 '16 at 15:54

answered Aug 26 '16 at 19:35

Gyandeep

12,726
4
31
42

1

Didn't seem like babel-eslint was needed – tjb Mar 13 '19 at 14:02
non-top-level imports are now part of the spec AND pervasively used – Merc May 10 '19 at 23:10
it's now supported by esline check [my answer](https://stackoverflow.com/a/58104827/912325) – Luizgrs Sep 25 '19 at 18:49

score 33 · Answer 2 · answered Aug 29 '18 at 12:08

33

my solution incase other dont work

"parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module"
}

answered Aug 29 '18 at 12:08

mayo19

647
8
16

score 20 · Answer 3 · answered Sep 25 '19 at 18:48

20

Support for dynamic import has been added in eslint 6.2.

You need to set ecmaVersion to 11 (or 2020) though.

"parserOptions": {
    "ecmaVersion": 11
    ...
}

You can test that in their online demo.

answered Sep 25 '19 at 18:48

Luizgrs

4,765
1
22
28

Would it work like this? "eslintConfig": { "extends": "react-app", "parserOptions": { "ecmaVersion": 11 } }, – Steven Matthews Feb 21 '20 at 04:08
3

That alone didn't work for me, I had to add the following line too - "sourceType": "module" – Roger Heathcote Sep 08 '20 at 14:56
it does work in the online demo with `sourceType: script` – Luizgrs Sep 09 '20 at 01:41
This is a more update to date answer. – College Code Jun 10 '23 at 19:40

score 4 · Answer 4 · edited Feb 26 '22 at 11:43

4

In my case:

Added javascriptreact for a react project. I guess the project type should be added to the plugins.

{
...,
 "plugins": [
        "prettier",
        "javascriptreact"
    ],
...
}

edited Feb 26 '22 at 11:43

ouflak

2,458
10
44
49

answered Feb 25 '22 at 13:16

A.Rodriguez

41
2

ignore eslint error: 'import' and 'export' may only appear at the top level

4 Answers4

Linked