[BUG] Outdated dependencies causing deprecation warnings in Jenkins build (Node.js 24 + npm 11)
- Dominant language
- JavaScript
- Stars
- 15.5k
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
## 🐛 Bug Report
ExcelJS 4.4.0 depends on deprecated packages that produce warnings during npm ci / npm install, creating noise in CI/CD pipelines and flagging in security review processes.
Lib version: 4.4.0 (latest as of 5 May 2026)
## Steps To Reproduce
```json
// package.json
{ "dependencies": { "exceljs": "^4.4.0" } }
```
```bash
# Install with Node 24 + npm 11
npm ci
```
### Output
```bash
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it.
npm warn deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities
npm warn deprecated fstream@1.0.12: This package is no longer supported.
npm warn deprecated glob@10.5.0: Old versions of glob are not supported
```
### Dependency chain
```bash
exceljs@4.4.0
├── archiver@5.3.2
│ └── glob@7.2.3
│ └── inflight@1.0.6
├── rimraf@2.7.1
│ └── glob@7.2.3 (duplicate)
└── unzipper@0.10.14
└── fstream@1.0.12
```
## The expected behaviour:
npm ci should complete without deprecation warnings from transitive dependencies. All internal dependencies should use actively maintained packages.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.