test: add library quality gates and package validation - #81
Open
terminalchai wants to merge 1 commit into
Open
Conversation
Signed-off-by: terminalchai <terminalchai@gmail.com>
terminalchai
force-pushed
the
test/80-package-quality-gates
branch
from
September 5, 2026 22:06
069b9f7 to
28978c6
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
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.
Closes #80.
Adds explicit
vue-tsc --noEmitchecking and a smoke test that packs the library, installs the tarball in a temporary consumer, imports the public entry point, resolves every current public subpath, checks required tarball files including CSS, and typechecks a consumer import. The existing CI workflows now usenpm ci, with typechecking, distribution validation, and package validation added to the build workflow.The consumer test exposed missing Vue component declarations in the packed artifact. Explicitly selecting the Vue declaration processor and declaring its
@vue/language-corepeer makes those declarations available. Node types are also declared directly, and two existing render-task mocks now include the required promise so the new typecheck passes. Public exports and component behavior are unchanged; repository strict mode is unchanged.Validation after a clean
npm ci, using Node 24.20.0 and npm 11.19.1:Vite still prints its existing advisory about future native config loading; all checks exit successfully.