Repository navigation
fix(maintenance): normalize package test scripts - #5653
Merged
Merged
Conversation
Scope unit scripts to unit test directories and standardize type, end-to-end, and placeholder commands across packages. Document the canonical forms so future packages avoid script drift.\n\nFixes #5643
This was referenced Sep 7, 2026
svozza
approved these changes
Sep 7, 2026
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.
Summary
Scope package unit-test scripts to
tests/unitand normalize test command conventions so unit runs cannot inadvertently execute end-to-end suites.Changes
tests/unit.echo 'Not Implemented'.vitest --run tests/types --typecheckand usevitest --runsyntax acrosspackages/*.CODING_STANDARDS.md.Issue number: closes #5643
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.