microsoft / microsoft/security-devops-azdevops

Npm deprecation warnings

Open
#127 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
86
Forks
22
PR merge metrics
No merged PRs in 30d

Description

The task is displaying the following deprecation warnings:

[Verbose]     Starting process: C:\Program Files\nodejs\npm.cmd
[Standard]     C:\Program Files\nodejs\npm.cmd install eslint@8.56.0 @microsoft/eslint-plugin-sdl@0.2.2 @microsoft/eslint-formatter-sarif@3.1.0 --prefix C:\VSTSAgent\_work\_msdo\packages\node_modules\eslint --global
[Trace]     Initializing sdterr...
[Trace]     Initializing sdtout...
[Trace]     Waiting for process to exit...
##[debug]Agent environment resources - Disk: C:\ Available 160602.86 MB out of 261642.00 MB, Memory: Used 4780.00 MB out of 16383.00 MB, CPU: Usage 57.00%
##[debug]Agent environment resources - Disk: C:\ Available 160601.32 MB out of 261642.00 MB, Memory: Used 4849.00 MB out of 16383.00 MB, CPU: Usage 52.00%
##[debug]Agent environment resources - Disk: C:\ Available 160597.32 MB out of 261642.00 MB, Memory: Used 4907.00 MB out of 16383.00 MB, CPU: Usage 72.00%
##[error]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.
##[debug]Processed: [Error]     ##vso[task.logissue type=error]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.
##[error]npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
##[debug]Processed: [Error]     ##vso[task.logissue type=error]npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
##[error]npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
##[debug]Processed: [Error]     ##vso[task.logissue type=error]npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
##[error]npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
##[debug]Processed: [Error]     ##vso[task.logissue type=error]npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
##[error]npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
##[debug]Processed: [Error]     ##vso[task.logissue type=error]npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
##[debug]Agent environment resources - Disk: C:\ Available 160569.71 MB out of 261642.00 MB, Memory: Used 4916.00 MB out of 16383.00 MB, CPU: Usage 81.00%
##[error]npm warn deprecated eslint@8.56.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
##[debug]Processed: [Error]     ##vso[task.logissue type=error]npm warn deprecated eslint@8.56.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
##[debug]Agent environment resources - Disk: C:\ Available 160558.66 MB out of 261642.00 MB, Memory: Used 4928.00 MB out of 16383.00 MB, CPU: Usage 73.00%
[Standard] 

We are using a self-hosted build agent which has the same NPM and node.js versions as the Microsoft hosted build agent installed:

NPM 10.8.2
Node 18.20.5

It looks like as if the task is installing and using deprecated packages. Please advise.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the npm install command and pinned package versions shown in the issue, then trace where the task defines or invokes that installation. Check whether the deprecated dependencies come from the task's direct versions or their transitive dependencies; the work is done when the task no longer emits these warnings on the stated Node.js and npm versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.