unique-filename
6.0.0 · 15 May 2026ISC29.1M / weekRepositoryHomepagenpmAtom feed
Upgrading unique-filename From 3.0.0 to 4.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
Other targets from 3.0.0Latest6.0.0
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 1
- fix
Before you upgrade
Tick each one off as you go- Breaking4.0.0
Release by release
- Breaking
unique-filenamenow supports node^18.17.0 || >=20.5.0 - Fixed
Align to npm 10 node engine range
- Breaking
4 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.