Vulnerability in eslint > espree > acorn
See original GitHub issueNPM audit is reporting a vulnerability in eslint accorn
dependency. Patch is available, but eslint
need to be updated.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Acorn dependency has a vulnerability on version v7.1.0 · Issue #435 ...
Problem According to https://www.npmjs.com/advisories/1488, this version of acorn has a vulnerability. Solution Bump it to version v7.1.1.
Read more >xinminlabs-espree - npm Package Health Analysis - Snyk
Acorn is a great JavaScript parser that produces an AST that is compatible with Esprima. Unfortunately, ESLint relies on more than just the...
Read more >Update our yarn dev dependencies to the extent allowed by ...
package name old version(s) new version(s)
@babel/code‑frame, 7.15.8, 7.16.7
@babel/compat‑data 7.15.0 7.17.0
@babel/core 7.15.8 7.17.0
Read more >Introduction to Node package manager - IBM Developer
Learn more about the Node.js ecosystem and use npm to find, install, and manage Node.js packages.
Read more >eslint | Yarn - Package Manager
ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This repository has a “^” before the eslint dependency declaration. It means all non breaking changes in eslint can be downloaded if new eslint versions become available.
The vulnerability has been fixed in eslint and a new version with no breaking change has been released. But maybe the older versions are forced in your packge-lock.json.
You could try as below: -> remove node_modules (maybe not needed) -> remove “rewire” from package.json -> npm install (“rewire” should disappear from package-lock.json) -> add “rewire” again to your package.json -> npm install (rewire will appear again in package-lock.json, but with new dependencies versions for rewire)
Unfortunately, this repo hasn’t been updated in quite a while. I maintain a fork that has the
eslint
updates already. Should be a drop-in replacement.