npm upgrade
Homeloader-utils 2 → 3
2.0.4 → 3.3.1. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
loader-utils 3.3.1 removes or renames exports your code may import.
- Removed
- 6
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 0
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 loader-utils@2.0.4..3.3.1
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.
- getCurrentRequestobject
- getOptionsobject
- getRemainingRequestobject
- parseQueryobject
- parseStringobject
- stringifyRequestobject
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 22, 2026. loader-utils on lurq.