Open apjanke opened 4 months ago
Notes:
npm ls --all
shows it's from glob@8.1.0, mocha@9.2.2 -> glob@7.2.0, and rimraf@3.0.2 -> glob@7.2.3.Progress:
Bumped all the other dependencies to their latest versions while I was at it; why not.
Got a resolution failure.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: octave-hacking@0.2.15-SNAPSHOT
npm error Found: eslint@9.6.0
npm error node_modules/eslint
npm error dev eslint@"^9.6.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/parser@7.15.0
npm error node_modules/@typescript-eslint/parser
npm error dev @typescript-eslint/parser@"^7.15.0" from the root project
npm error peer @typescript-eslint/parser@"^7.0.0" from @typescript-eslint/eslint-plugin@7.15.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error dev @typescript-eslint/eslint-plugin@"^7.15.0" from the root project
Downgraded my package.json dep to "eslint": "^8.56.0". Made that go away. Now it solves. But I'm still getting warnings.
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
Some of those are getting pulled in by eslint ^8.56.0. I don't know how to upgrade to eslint 9.x due to the above error, so I guess I'll just live with this and see how it works.
Time to bump the dependencies, since it's been a while.
When doing
npm install
with the current deps in package.json, I get these warnings:I'm using
"^2.3.4"
style "compatible with" version specifiers. Maybe I should switch to>=
specifiers, version ranges capped by the next major version, or something else that allows more flexibility? I'm not sure what the "^" "compatible with" does; it's not documented in the "see semver" link on the package.json doco page or on that page itself.Progress
Work is on branch "early-2024".