sort() is a stable sort, so this library is deprecated
Opened this issue · 0 comments
Describe the bug
I know creating a library relying on some other libs and API sometimes might lead such kind of situations where some kind of deprecations happen. But this is fixable I think. I don't know how to fix but you know. So, sharing the issue here as bug report.
Thanks for taking some time to see this.
When I want to install I this library got this:
PS C:\ui\test> npm i -D vite-plugin-checker
npm warn deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm warn deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
added 337 packages, changed 1 package, and audited 412 packages in 1m
54 packages are looking for funding
run npm fund
for details
found 0 vulnerabilities
PS C:\ui\test>
Reproduction
Just install with npm i -D vite-plugin-checker
and you get this error:
PS C:\ui\test> npm i -D vite-plugin-checker
npm warn deprecated stable@0.1.8: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm warn deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
added 337 packages, changed 1 package, and audited 412 packages in 1m
54 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
PS C:\ui\test>
Expected behavior
Expected to see without any warning or errors and working perfectly without issues and deprecations.
System Info
System:
OS: Windows 11 10.0.22631
CPU: (8) x64 Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
Memory: 3.78 GB / 15.74 GB
Binaries:
Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
pnpm: 8.14.1 - ~\AppData\Local\pnpm\pnpm.CMD
npmPackages:
vite-plugin-checker: ^0.7.2 => 0.7.2
Additional context
Validations
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.