fix: includePackages fails with vue-component-meta 3.3 and update it - #213
Merged
Conversation
vue-component-meta 3.3 only reads files that belong to the tsconfig project or were registered explicitly. Components pulled in via `includePackages` live in node_modules, which the project tsconfig does not cover, so they dropped out of the component index with "is not part of the project". Register such a file with the checker and retry, so package components keep being indexed.
fago
changed the title
fago
changed the title
fago
changed the title
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
2 participants
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.
Upgrades
vue-component-meta3.2.9 → 3.3.9, and fixes the behaviour change it introduces.The breakage
vue-component-meta 3.3 only reads files that belong to the tsconfig project or were registered explicitly. Components pulled in via
includePackageslive innode_modules, which the project tsconfig does not cover — so they silently dropped out of the component index:This is a real regression for consumers using
includePackages, not just a test failure — the affected components disappear fromcomponent-index.json.The fix
generateComponentIndexnow registers such a file with the checker (updateFile) and retries, so package components keep being indexed. Unrelated errors still propagate.Verification
Run locally on this branch:
includePackagescases that fail without the fix)🤖 Generated with Claude Code
https://claude.ai/code/session_0135TzeJ5xX7vdwouF9Qd6yv