-
-
Notifications
You must be signed in to change notification settings - Fork 2
ci: Add workflow for build/lint/typecheck/test #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Add workflow for build/lint/typecheck/test #25
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
💡 Enable Vercel Agent with $100 free credit for automated AI reviews |
This pull request introduces automated continuous integration (CI) for the project using GitHub Actions, and enhances the test coverage reporting setup across multiple packages. The main improvements are the addition of a CI workflow, integration of the
@vitest/coverage-v8provider for code coverage, and updates to dependencies and lock files to support these changes.CI Workflow Integration
.github/workflows/ci.ymlfile that defines jobs for linting, type checking, testing (with coverage reporting), and building the project. The workflow runs on pushes, pull requests, and manual dispatch, and includes concurrency management to cancel redundant runs.Test Coverage Configuration
config/vite/vite.config.jsto enable V8-based coverage reporting in Vitest by specifying thecoverageprovider as"v8".@vitest/coverage-v8as a devDependency and peerDependency inconfig/vite/package.json, and as a devDependency in multiple engine packages (core,cli,loader,styleframe,transpiler) to ensure coverage support in all relevant workspaces. [1] [2] [3] [4] [5] [6]Dependency and Lock File Updates
pnpm-lock.yamlto add the new dependencies (@vitest/coverage-v8,@codecov/vite-plugin, and related packages) and reflect the changes in all affected importers and packages. This ensures consistent installation and usage of the new coverage tooling and CI dependencies. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]These changes collectively automate CI processes, improve code quality checks, and enable robust code coverage reporting throughout the monorepo.