npm upgrade
Homealien-signals 0 → 1
0.6.0 → 1.0.13. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
alien-signals 1.0.13 removes or renames exports your code may import.
- Removed
- 20
- 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 alien-signals@0.6.0..1.0.13
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.
- Computedclass
- Effectclass
- EffectScopeclass
- Signalclass
- activeEffectScopeobject
- activeSubobject
- checkDirtyfunction
- drainQueuedEffectsfunction
- endTrackfunction
- isDirtyfunction
- linkfunction
- propagatefunction
- runInnerEffectsfunction
- setActiveScopefunction
- setActiveSubfunction
- shallowPropagatefunction
- startTrackfunction
- unstableobject
- untrackfunction
- untrackScopefunction
Signature changes
Still exported, but the number of arguments it reads changed.
- effectScope0 → 1 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 17, 2026. alien-signals on lurq.