npm upgrade
Home@nodelib/fs.stat 1 → 2
1.1.3 → 2.0.5. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@nodelib/fs.stat 2.0.5 removes or renames exports your code may import.
- Removed
- 1
- Renamed
- 0
- Signature changes
- 1
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 1
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade @nodelib/fs.stat@1.1.3..2.0.5
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- statCallbackfunction
Signature changes
Still exported, but the number of arguments it reads changed.
- stat2 → 3 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 8, 2026. @nodelib/fs.stat on lurq.