Skip to content

Conversation

@alexgrozav
Copy link
Contributor

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-v8 provider for code coverage, and updates to dependencies and lock files to support these changes.

CI Workflow Integration

  • Added a new .github/workflows/ci.yml file 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

  • Updated config/vite/vite.config.js to enable V8-based coverage reporting in Vitest by specifying the coverage provider as "v8".
  • Added @vitest/coverage-v8 as a devDependency and peerDependency in config/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

  • Updated pnpm-lock.yaml to 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.

@alexgrozav alexgrozav self-assigned this Oct 20, 2025
@alexgrozav alexgrozav linked an issue Oct 20, 2025 that may be closed by this pull request
@changeset-bot
Copy link

changeset-bot bot commented Oct 20, 2025

⚠️ No Changeset found

Latest commit: 02a6a2e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Oct 20, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
styleframe-dev-production Ready Ready Preview Comment Oct 20, 2025 7:22pm

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

@alexgrozav alexgrozav merged commit 43df1e1 into main Oct 20, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Set up GitHub workflow to check build, lint, and tests for each PR

2 participants