multiple deprecated dependecy versions
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 16
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
There are multiple dependecys that are deprecated, we should probably go through the list and update them
npm warn exec The following package was not found and will be installed: npcheck@1.0.1
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE package: '@pkgjs/support@0.0.[5](https://github.com/nodeshift/nodejs-reference-architecture/actions/runs/9746719712/job/26897742131#step:4:6)',
npm warn EBADENGINE required: { node: '^14 || ^13 || ^12 || ^11 || ^10.19' },
npm warn EBADENGINE current: { node: 'v20.15.0', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn deprecated osenv@0.1.5: This package is no longer supported.
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated inflight@1.0.[6](https://github.com/nodeshift/nodejs-reference-architecture/actions/runs/9746719712/job/26897742131#step:4:7): 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 @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated uuid@3.4.0: Please upgrade to version [7](https://github.com/nodeshift/nodejs-reference-architecture/actions/runs/9746719712/job/26897742131#step:4:8) or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v[8](https://github.com/nodeshift/nodejs-reference-architecture/actions/runs/9746719712/job/26897742131#step:4:9).dev/blog/math-random for details.
npm warn deprecated debuglog@1.0.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated readdir-scoped-modules@1.1.0: This functionality has been moved to @npmcli/fs
npm warn deprecated read-package-json@6.0.4: This package is no longer supported. Please use @npmcli/package-json instead.
npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm warn deprecated are-we-there-yet@4.0.2: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated gauge@5.0.2: This package is no longer supported.
npm warn deprecated read-installed@4.0.3: This package is no longer supported.
npm warn deprecated npmlog@7.0.1: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v[9](https://github.com/nodeshift/nodejs-reference-architecture/actions/runs/9746719712/job/26897742131#step:4:10) are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm warn deprecated read-package-json@2.1.2: This package is no longer supported. Please use @npmcli/package-json instead.
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated gauge@2.7.4: This package is no longer supported.
1.0.1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files or tests; start by inspecting the repository's dependency manifests and tracing the deprecated packages listed in the npm output. Update the applicable dependency declarations, then run npcheck again and confirm the reported deprecation warnings have been resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100