Babel ES-Lint parse errors in imported module. Cannot find module './parse-with-patch'

Question

I have been searching Github and Stack Overflow for the past hour with no answer on how to fix this problem with ES-Lint.

.eslintrc.json

{
  "parser": "babel-eslint",
  "extends": ["airbnb", "prettier"],
  "plugins": ["prettier", "flowtype"],
  "rules": {
    "prettier/prettier": ["error"],
    "no-unused-expressions": 0,
    "react/jsx-filename-extension": 0,
    "class-methods-use-this": 0,
    "default-case": 0,
    "import/no-unresolved": 0,
    "react/prefer-stateless-function": 0,
    "import/no-named-as-default": 0
  },
  "parserOptions": {
    "sourceType": "module",
    "import/extensions": [".jsx", ".js"],
    "allowImportExportEverywhere": true
  }
}

devDependencies

"devDependencies": {
    "@babel/plugin-transform-runtime": "^7.1.0",
    "babel-eslint": "^10.0.1",
    "eslint": "^5.7.0",
    "eslint-config-airbnb": "^17.1.0",
    "eslint-config-prettier": "^3.1.0",
    "eslint-plugin-flowtype": "^2.34.1",
    "eslint-plugin-import": "^2.14.0",
    "eslint-plugin-jsx-a11y": "^6.0.2",
    "eslint-plugin-prettier": "^3.0.0",
    "eslint-plugin-react": "^7.11.1",
    "flow-bin": "0.78.0",
    "jest": "23.5.0",
    "jest-react-native": "18.0.0",
    "metro-react-native-babel-preset": "^0.45.0",
    "prettier": "1.14.1",
    "react-native-debugger-open": "0.3.17",
    "react-test-renderer": "16.0.0-alpha.12",
    "schedule": "0.4.0",
    "semver": "5.5.0"
  },

All of the linter options are working which is great, but there is no way I can let other people use this config if I am getting errors for every single import statement throughout the entire app.

Does anyone have any idea what could be going on?

Seeing same. Started happening after some updates today. It was either the update to Node 11 or just the general dependency updates. It isn't all of my imports, only the ones where I am importing a default export. — Mac
– Mac, Commented Oct 31, 2018 at 1:02
No, IntelliJ. It might be Node. I'm not getting the error on TravisCI, which is still using Node 10. — Mac
– Mac, Commented Oct 31, 2018 at 19:07
I eliminated the Node version as the culprit. It looks like there might be some incompatibility with Babel 7.1. I had various other (serious) problems until I reverted my dependencies and got back to Babel 7.0. This ESLint issue also seems to be fixed now. — Mac
– Mac, Commented Oct 31, 2018 at 22:18
I fixed mine but I honestly dont remember what I did. Did you check to see if you had eslint installed in your global npm dependencies? It might be trying to use that version. I honestly don't remember what fixed my problem. — Dan Zuzevich
– Dan Zuzevich, Commented Oct 31, 2018 at 22:21

alexfertel · Accepted Answer · 2021-07-03 13:08:54Z

7

These steps might work:

Change path to path.ts
Save
Again, change it to path
Save

edited Jul 3, 2021 at 13:08

alexfertel

9461 gold badge10 silver badges23 bronze badges

answered Jul 2, 2021 at 15:34

Darshan patel

711 silver badge2 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

kevbost Over a year ago

This actually worked for me with error: Parse errors in imported module 'filename.ts': ',' expected. import/namespace Wish i knew why... but now i'm just glad it's gone.

Alex Varghese · Accepted Answer · 2020-02-25 08:08:19Z

3

Just disable that rule to rrsolve this issue insted of uninstalling ESLint

"Unfortunately, React + Redux is the most common scenario. However, there are lots of other cases where HOCs will force developers to shut down this rule."

https://github.com/benmosher/eslint-plugin-import/issues/544

https://github.com/reactjs/react-redux/issues/119

https://github.com/18F/calc/pull/1235

.eslintrc

"rules": {
    "import/no-named-as-default": 0
}

answered Feb 25, 2020 at 8:08

Alex Varghese

2,28019 silver badges18 bronze badges

Comments

Udi · Accepted Answer · 2020-11-25 12:44:59Z

1

Deleting node_modules and reinstalling everything worked for me :-(

answered Nov 25, 2020 at 12:44

Udi

30.8k9 gold badges105 silver badges134 bronze badges

Comments

Md. Shafiqul Islam · Accepted Answer · 2022-07-31 07:01:46Z

1

just add in your eslint rules. Works fine for me

"parser": "off",

answered Jul 31, 2022 at 7:01

Md. Shafiqul Islam

4041 gold badge6 silver badges12 bronze badges

Comments

Axel Douglas · Accepted Answer · 2021-12-28 14:51:08Z

0

babel-eslint has been deprecated. Update to @babel/eslint-parser.

https://tjaddison.com/blog/2021/03/updating-babel-eslint-to-babeleslint-parser-for-react-apps/

answered Dec 28, 2021 at 14:51

Axel Douglas

1

1 Comment

Aishwarya Over a year ago

Please add explanation with/or screen-capture or code. Sharing link over question may invalid after period of time, which tends to invalid answer.

Alex · Accepted Answer · 2018-11-02 08:33:37Z

-7

Uninstalling EsLint globally fixed my problem: npm uninstall -g eslint

answered Nov 2, 2018 at 8:33

Alex

212 bronze badges

3 Comments

Dan Zuzevich Over a year ago

Yeah, I think that should solve the problem for most people. Also, a really annoying gotcha is that I had to close and reopen VSCode before the settings took effect. Might be worthwhile for people to remove es lint globally then close and reopen their editor just in case.

Alex Varghese Over a year ago

Uninstalling EsLint is not a good practice. ESLint is used for ensuring code quality in the application. Uninstalling that not making any sense

Dan Zuzevich Over a year ago

Think people misunderstood this. I believe Alex meant uninstall the global version of eslint, and use the local version declared in the package.json.

Collectives™ on Stack Overflow

Babel ES-Lint parse errors in imported module. Cannot find module './parse-with-patch'

6 Answers 6

1 Comment

Comments

Comments

Comments

1 Comment

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

1 Comment

Comments

Comments

Comments

1 Comment

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related