dependencies deprecated - upgrades possible?

[OzBob]

upon installing 3.35.0 via npm the following warnings were displayed

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 rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

Will these dependencies be upgraded?

1. inflight@1.0.6
2. rimraf@3.0.2
3. glob@7.2.3
4. uuid@3.4.0

[timtucker-dte]

Duplicate of #2500

Still would be good to know when there's an update coming, though

[jainakanksha-msft]

OzBob, the uuid vulnerability has been fixed.
We’ll plan the remaining items.
If you have any specific use case related to these dependencies, let us know

[OzBob]

Akanksha Jain (@jainakanksha-msft) thank you for updating the uuid reference.

re "specific use case": no - but when a package warns about memory leaks you could choose to not believe them, or you could update.

I went into the back log of issues for "inflight" and this is the memory leak issue: isaacs/inflight-DEPRECATED-DO-NOT-USE#18

but as the whole package has been deemed deprecated: https://github.com/isaacs/inflight-DEPRECATED-DO-NOT-USE

As they say

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.

Please add to your "plan" upgrade:

Azurite/package-lock.json

Line 6541 in bf3ba03

"inflight": "^1.0.4",

to use
https://www.npmjs.com/package/inflight-lru

[jainakanksha-msft]

OzBob we'll take a look into this. Thanks for sharing the information.
For your information, Azurite welcomes contributions.
If you'd like to raise a PR to fix this, we could plan to include it in an upcoming release.