npm upgrade
Homets-node 9 → 10
9.1.1 → 10.9.2. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
ts-node 10.9.2 removes or renames exports your code may import.
- Removed
- 4
- Renamed
- 0
- Signature changes
- 1
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 3
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 ts-node@9.1.1..10.9.2
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.
- getExtensionsfunction
- normalizeSlashesfunction
- parsefunction
- splitfunction
Signature changes
Still exported, but the number of arguments it reads changed.
- register0 → 1 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 10, 2026. ts-node on lurq.