@npmcli/move-file
3.0.0 · 14 Oct 2022MIT9.5M / weekRepositoryHomepagenpmAtom feed
Where each line stands
Plan an upgradeWhat to use instead
Named in the deprecation message
Read from the message, so worth a look before switching.
Before you switch
- 1
Check what else depends on it
Paste your package.json in the dependency check to see every deprecated or outdated package in one pass, not only this one.
- 2
Read the replacement's peers and releases
The page of @npmcli/fs lists what it works with, its recent release notes and any open advisory.
- 3
Know when it ships
Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.
Latest releases
- 3.x · latest line
3.0.0
14 Oct 2022- Breaking
@npmcli/move-fileis now compatible with the following semver range for node:^14.17.0 || ^16.13.0 || >=18.0.0 Postinstall for dependabot template-oss PR
- 2.x · maintenance
2.0.1
15 Aug 2022Linting
2.0.0
5 Apr 2022- Breaking
This drops support for node 10 and non-LTS versions of node 12 and node 14
Breaking changes
- Breaking
This drops support for node 10 and non-LTS versions of node 12 and node 14
Dependency tracking
Know when your own dependencies move
This page watches @npmcli/move-file. inlinr reads your package.json and keeps the same watch on every dependency you declare, then tells you only what needs you.
Advisories reach you
An email when a critical or high advisory affects a project, before the next install.
Upgrades checked first
Peer ranges, Node, ESM-only and types changes read before you bump.
Only what matters
Majors and breaking notes stay; patches and sibling bumps fold into one line.
Reading releases, release notes and advisories…
Registry facts last checked 20 Nov 2026. Releases and advisories last read 20 Nov 2026.
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.