chore(deps): upgraded to latest dependencies

[Sourav-kashyap]

Description

Upgraded loopback4-ratelimiter to use the latest versions of rate-limiting dependencies, migrate from older versions to the latest stable releases.

Checklist:

• Performed a self-review of my own code
• npm test passes on your machine

Build Passed:

TestCases Passed:

[yeshamavani]

can this be removed all together

[Sourav-kashyap]

resolved

[yeshamavani]

@Sourav-kashyap trivy failing

[sonarqubecloud]

SonarQube reviewer guide

Summary: Upgrade dependencies significantly, including express-rate-limit from v6 to v8, and update related packages to compatible versions.

Review Focus:

• express-rate-limit v8 introduces breaking changes: the name option is no longer supported, and store instances cannot be reused. The code now caches RateLimiter instances and filters unsupported options.
• Type definitions have changed for rate-limit stores (MemcachedStore, RedisStore now use named exports).
• Node.js minimum version bumped to 20 for several dependencies (husky, commitlint, jsdom, typescript).
• Major dependency updates: jsdom (21 → 29), typescript (5.2.2 → 5.5.4), husky (7 → 9), semantic-release plugins updated.

Start review at: src/providers/ratelimit-datasource.provider.ts. This file is critical because it handles the creation of rate-limit stores (Memcached, Mongo, Redis) and demonstrates how to work with the updated package imports and types.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
48.4% Duplication on New Code

See analysis details on SonarQube Cloud