mathworks / mathworks/MATLAB-language-server

warnings for deprecated packages

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

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
125
Forks
21
PR merge metrics
No merged PRs in 30d

Description

I am using npm v11.6.0. npm install produces several deprecated package warnings.

$ npm install
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 eslint-config-standard-with-typescript@22.0.0: Please use eslint-config-love, instead.
npm warn deprecated @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 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 eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options.

> matlab-language-server@1.3.5 postinstall
> cd src/licensing/gui && npm install && cd ../../..


up to date, audited 720 packages in 766ms

161 packages are looking for funding
  run `npm fund` for details

1 low severity vulnerability

To address all issues, run:
  npm audit fix

Run `npm audit` for details.

added 539 packages, and audited 540 packages in 3s

132 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
$ npm audit fix

up to date, audited 540 packages in 624ms

132 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
$ npm --version
11.6.0

Contributor guide

Open the contributing guide

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

Reproduce the report with npm v11.6.0 by running npm install and record which deprecated-package warnings remain, including the postinstall step under src/licensing/gui. Trace the reported packages through the project’s dependency manifests; done means the obsolete warnings are removed or replaced and npm audit remains clean.

Written by the indexing model from the issue text.

Assessment

Tech stack
eslint, typescript
Domain
build-system, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.