Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Out of date eslint plugin causes Parsing error: Cannot read property 'map' of undefined #9583

Closed
radiosilence opened this issue Sep 2, 2020 · 4 comments · Fixed by #9434
Closed

Comments

@radiosilence
Copy link

radiosilence commented Sep 2, 2020

Describe the bug

I've upgraded my project's TypeScript to version 4. It seems this creates an issue because react-scripts @typescript-eslint/parser is out of date. Could we bump these packages?

Currently I am doing this in my package.json:

  "resolutions": {
    "**/@typescript-eslint/parser": "4.0.1",
    "**/@typescript-eslint/eslint-plugin": "4.0.1"
  },

as a workaround.

@radiosilence radiosilence changed the title Out of date eslint causes Parsing error: Cannot read property 'map' of undefined Out of date eslint plugin causes Parsing error: Cannot read property 'map' of undefined Sep 2, 2020
@thien-do
Copy link
Contributor

thien-do commented Sep 2, 2020

The resolutions is for Yarn, for NPM uses https://docs.npmjs.com/cli/shrinkwrap or https://www.npmjs.com/package/npm-force-resolutions

Anyway look like CRA is using version 2 of the plugin.. that means 2 major versions of the plugin and 1 major version of eslint we're behind

@radiosilence
Copy link
Author

Yeah it is quite a way behind. What would be the negatives of bumping it?

@radiosilence
Copy link
Author

#9590 Submitted a PR. Wonder when all the builds will start working :S

JaninaWibker added a commit to JaninaWibker/spreadsheets that referenced this issue Sep 6, 2020
WARNING: broken build atm because eslint-typescript is broken / out of date in create-react-app (facebook/create-react-app#9583)
@thien-do
Copy link
Contributor

I've just realized the PR is tagged with v4 :( is there any chance we can still have this in v3?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants