@babel/core: Upgrade json5 to 2.1.2
See original GitHub issueIn @babel/core 7.8.7, the current version of json5 (2.1.1) depends on a version of minimist that contains the security vulnerability CVE-2020-7598. Can we update json5 to 2.1.2 to resolve this?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Babel issue running npm run dev after upgrade to Mix
I have an old Laravel App which I updated to Laravel 5.8. I removed all old resources files, package-lock.json, yarn.lock and gulp files....
Read more >Fail to install npm packages if i keep the package-lock.json file ...
i tried to clear the npm cach using npm cach clear --force and remove the node_modules but not solved the problem (it's run...
Read more >package-lock.json - plugins/simple-submit-rules - Git at Google
"resolved": "https://registry.npmjs.org/@types/json5/-/json5-0.0.29.tgz", ... "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.5.4.tgz",.
Read more >package-lock.json - AWS Code Sample
... "resolved": "https://registry.npmjs.org/@babel/core/-/core-7.18.9.tgz", ... "https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz", ...
Read more >yarn.lock · master · GitLab.com / www-gitlab-com
resolved "https://registry.yarnpkg.com/@babel/core/-/core-7.12.10.tgz#b79a2e1b9f70ed3d84bbfb6d8c4ef825f606bccd" ... json5 "^2.1.2". 34. lodash "^4.17.19".
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 Free
Top 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

pushed fsevents 1.2.12
@adamu
There is a problem here: we can’t upgrade to
chokidarv3 in Babel 7 because it contains breaking changes that would be reflected to our users.@babel/clihas an optional dependency onchokidar@^2.1.8.chokidar@2.1.8has an optional dependency onfsevents@^1.2.7fsevents@1.2.11bundles all its dependencies, includingminimist@0.0.8There are a few solutions:
yarn, you could try to force achokidar@3upgrade using theresolutionsfield inpackage.json. Maybe the breaking change doesn’t affect you.npm, you can try usingnpm-force-resolutionsto force achokidar@3upgrade.npm auditwill still complain, but you won’t actually have the unsecure code.npm --no-optionalto avoid installingchokidar@2(you might first have to delete yourpackage-json.lock)fseventsmaintainers to release afsevents@1.2.12version, which would be automatically picked up bychokidar@2. Even if the last version is2.1.2, it looks like the v1 release line is still maintained.