Open jeff00seattle opened 2 years ago
@jeff00seattle
I have resolved all possible deprecations now. The only ones left are as follows:
$ npm ci
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. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated puppeteer@18.1.0: < 19.4.0 is no longer supported
> cypress-example-kitchensink@0.0.0-development prepare
> node ./scripts/prepare.js
husky - HUSKY env variable is set to 0, skipping install
added 885 packages, and audited 1096 packages in 1m
146 packages are looking for funding
run `npm fund` for details
2 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
$ npm audit
# npm audit report
got <11.8.5
Severity: moderate
Got allows a redirect to a UNIX socket - https://github.com/advisories/GHSA-pfrx-2q88-qq97
fix available via `npm audit fix --force`
Will install netlify-plugin-cypress@1.2.0, which is a breaking change
node_modules/got
netlify-plugin-cypress >=1.3.0-beta.1
Depends on vulnerable versions of got
node_modules/netlify-plugin-cypress
2 moderate severity vulnerabilities
To address all issues (including breaking changes), run:
npm audit fix --force
The original report "npm install: package.json, upgrade dependencies, too many deprecated sources" is no longer accurate, especially "too many deprecated sources". There are now only two deprecation warnings, caused by one package, and this can't be resolved here at the moment.
For the sake of clarity I suggest closing this issue and following up with #708.
This issue is resolved and should be closed. There is only one minor deprecation left:
$ npm ci
npm warn deprecated read-pkg-up@11.0.0: Renamed to read-package-up
> cypress-example-kitchensink@0.0.0-development prepare
> node .husky/install.mjs
added 658 packages, and audited 864 packages in 40s
171 packages are looking for funding
run `npm fund` for details
4 vulnerabilities (1 moderate, 3 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
Request Audit and upgrade
package.json
's dependencies and create newpackage-lock.json
.Too many uncomfortable warnings.
Tried performing
npm audit fix --force
, made it worse, and required to start fresh with a new clone.