npm upgrade
Home@unhead/vue 0 → 1
0.7.1 → 1.11.20. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
@unhead/vue 1.11.20 removes or renames exports your code may import.
- Removed
- 25
- Renamed
- 0
- Signature changes
- 0
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 8
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 @unhead/vue@0.7.1..1.11.20
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.
- VueReactiveUseHeadPluginfunction
- asArrayfunction
- headSymbolprimitive
- useBodyAttrsfunction
- useHtmlAttrsfunction
- useServerBodyAttrsfunction
- useServerHtmlAttrsfunction
- useServerTagBasefunction
- useServerTagLinkfunction
- useServerTagMetafunction
- useServerTagMetaFlatfunction
- useServerTagNoscriptfunction
- useServerTagScriptfunction
- useServerTagStylefunction
- useServerTagTitlefunction
- useServerTitleTemplatefunction
- useTagBasefunction
- useTagLinkfunction
- useTagMetafunction
- useTagMetaFlatfunction
- useTagNoscriptfunction
- useTagScriptfunction
- useTagStylefunction
- useTagTitlefunction
- useTitleTemplatefunction
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Oct 7, 2026. @unhead/vue on lurq.