@npmcli/fs
6.0.0 · 15 May 2026ISC40.4M / weekRepositoryHomepagenpmAtom feed
Upgrading @npmcli/fs From 2.1.0 to 6.0.0
8 releases in betweenevery note read
Reading releases, release notes and advisories…
- 8
- changes to make
- 0
- advisories fixed
- 6
- new
- 3
- fixes
Before you upgrade
Tick each one off as you go- Breaking6.0.0
- Breaking6.0.0
- Breaking5.0.0
- Breaking4.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking2.1.1
Release by release
- Breaking
@npmcli/fsnow supports node^22.22.2 || ^24.15.0 || >=26.0.0 - Breaking
template-oss-apply
- New
Bump to new node engine range
- Breaking
- Breaking
@npmcli/fsnow supports node^20.17.0 || >=22.9.0 - Fixed
Align to npm 11 node engine range
- Breaking
- Breaking
@npmcli/fsnow supports node^18.17.0 || >=20.5.0 - Fixed
Align to npm 10 node engine range
- Breaking
3.1.1nothing new or fixed in the note
- New
Port @npmcli/move-file
- New
Add readdirScoped method
- New
- Breaking
This package no longer exports the full set of core fs functions
- Breaking
This removes the
owneroption from all methods that previously supported it, as well as thewithOwnerandwithOwnerSyncmethods - Breaking
@npmcli/fsis now compatible with the following semver range for node:^14.17.0 || ^16.13.0 || >=18.0.0 - New
Remove custom promisification in favor of fs/promises
- New
Remove owner related code as well as stale polyfills
- New
Postinstall for dependabot template-oss PR
- Breaking
- Fixed
Linting
- Fixed
- Breaking
Remove polyfills which are out of range of our engines
- Breaking
11 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.