unique-filename
6.0.0 · 15 May 2026ISC29.1M / weekRepositoryHomepagenpmAtom feed
Upgrading unique-filename From 3.0.0 to 6.0.0
3 releases in betweenevery note read
Reading releases, release notes and advisories…
- 4
- changes to make
- 0
- advisories fixed
- 1
- new
- 2
- fixes
Before you upgrade
Tick each one off as you go- Breaking6.0.0
- Breaking6.0.0
- Breaking5.0.0
- Breaking4.0.0
Release by release
- Breaking
unique-filenamenow supports node^22.22.2 || ^24.15.0 || >=26.0.0 - Breaking
template-oss-apply
- New
Bump to new node engine range
- Breaking
- Breaking
unique-filenamenow supports node^20.17.0 || >=22.9.0 - Fixed
Align to npm 11 node engine range
- Breaking
- Breaking
unique-filenamenow supports node^18.17.0 || >=20.5.0 - Fixed
Align to npm 10 node engine range
- Breaking
9 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.