npm warnings for react-static 7.6.2 #1638
Replies: 2 comments
-
from cli: $react-static create Using React Static template: basic [✓] Project "react-static-proof" created (123.8s) More unmet dependencies ... i guess package.json for react-static needs some more updates ... |
Beta Was this translation helpful? Give feedback.
-
$ npm run start
Starting Development Server... Why you should do it regularly: Why you should do it regularly:
Bundling application for Production... Browserslist: caniuse-lite is outdated. Please run: Why you should do it regularly: Why you should do it regularly: Why you should do it regularly: Why you should do it regularly: Your app is now exported! Here's what we suggest doing next:
$ npm run serve
UPDATE AVAILABLE The latest version of ┌──────────────────────────────────────────────────┐ $ sudo apt install xsel $ npm run serve
UPDATE AVAILABLE The latest version of ┌──────────────────────────────────────────────────┐ |
Beta Was this translation helpful? Give feedback.
-
Hi all,
Global installation of react-static gives some npm warning listed below, some are simply deprecation warnings, others warn for breakage and/or just recommend upgrading some of the dependencies, such as: chokidar, debug, html-webpack-plugin, uuid, svgc and core-js ...
************************************************** NPM WARNINGS ***************************************************************
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (debug-js/debug#797)
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated html-webpack-plugin@3.2.0: 3.x is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated core-js@2.6.12: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
What is the best way to deal with this ... changing the minimum version number of the dependencies in the package.json file for this package and hope it doesnt break stuff ?
Cheers
jwd
Beta Was this translation helpful? Give feedback.
All reactions