chore(deps): upgrade nuxt-component-meta to 0.18.0 - #554
Open
hendrikheil wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
0.18.0 brings vue-component-meta 3.3.11, whose `PropertyMetaSchema` union gained a `literal` variant with no `schema` property. Narrow the two array/object guards in props.ts with an `in` check. Bump vue to ^3.5.42 so the graph converges on one instance. Re-resolving for the upgrade otherwise leaves vue split across 3.5.35 and 3.5.42, which duplicates @tiptap/vue-3 and vue-i18n and fails the app typecheck on ~150 mismatched-instance errors. 3.5.42 already satisfied the existing ^3.5.35 range; 3.5.35 was lockfile inertia. Converging surfaces two real type errors, both fixed here: the Collapsible `open` model is `boolean | undefined` (defineModel with `default: undefined`), and formTreeWithValues widened `type` to `string` without an explicit FormTree annotation. Claude-Session: https://claude.ai/code/session_013rF9ZZvHV78RAHZudZZNZH
hendrikheil
force-pushed
the
chore/upgrade-nuxt-component-meta
branch
from
September 3, 2026 08:26
3eccea4 to
1700066
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
nuxt-component-meta0.17.2 → 0.18.0 (adds theextendComponentMetamacro;docusalready pulled it transitively).Two fixes were needed to land it:
props.ts— 0.18.0 pullsvue-component-meta3.3.11, whosePropertyMetaSchemagained aliteralvariant with noschema. Narrowed both guards with anincheck.vue→^3.5.42— re-resolving splits vue across 3.5.35/3.5.42, duplicating@tiptap/vue-3andvue-i18nand failing typecheck with ~150 mismatched-instance errors. 3.5.42 already satisfied the old range; 3.5.35 was lockfile inertia. Converging surfaced 2 real type errors, both fixed.pnpm verifypasses — lint, prepack, typecheck, 393 tests. Typecheck is clean onmainand clean here.Note:
nuxt-module-build build src/modulefails withTS2742on thestudio.clientplugins. Pre-existing onmain, masked becauseprepackjoins its commands with;not&&. Worth a separate fix.