Packages

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…

  1. 3.0.0yours
  2. 4.0.0major
  3. 5.0.0major
  4. 6.0.0target

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

  1. 6.0.0

    Migration needed15 May 20261 new
    • Breaking

      unique-filename now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

    • Breaking

      template-oss-apply

    • New

      Bump to new node engine range

  2. 5.0.0

    Migration needed22 Oct 20251 fix
    • Breaking

      unique-filename now supports node ^20.17.0 || >=22.9.0

    • Fixed

      Align to npm 11 node engine range

  3. 4.0.0

    Migration needed26 Sep 20241 fix
    • Breaking

      unique-filename now supports node ^18.17.0 || >=20.5.0

    • Fixed

      Align to npm 10 node engine range

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.