Skip to content

chore: update @withstudiocms/buildkit to version 0.1.0-beta.4 and remove test-scripts package#36

Merged
Adammatthiesen merged 3 commits intomainfrom
update-build-kit
Aug 26, 2025
Merged

chore: update @withstudiocms/buildkit to version 0.1.0-beta.4 and remove test-scripts package#36
Adammatthiesen merged 3 commits intomainfrom
update-build-kit

Conversation

@Adammatthiesen
Copy link
Member

@Adammatthiesen Adammatthiesen commented Aug 26, 2025

This pull request removes the custom test-scripts package and migrates test running in the web-vitals package to use the buildkit test command instead. It also updates the @withstudiocms/buildkit dependency to a newer version and cleans up related dependencies and configuration files.

Migration to buildkit for testing:

  • The web-vitals package now uses buildkit test instead of the custom test-scripts command to run tests, simplifying the test workflow.
  • The entire test-scripts package is removed, including its source files, configuration, and dependencies. [1] [2] [3] [4] [5]

Dependency and lockfile updates:

  • Upgrades @withstudiocms/buildkit from 0.1.0-beta.1 to 0.1.0-beta.4 in both package.json and pnpm-lock.yaml, and updates its dependencies accordingly. [1] [2] [3] [4]
  • Removes references to the now-deleted test-scripts package from the monorepo lockfile. [1] [2]

Minor lockfile cleanup:

  • Removes the unused cpu field from the libsql dependency in the lockfile.

Summary by CodeRabbit

  • Chores

    • Updated build tooling to the latest beta for improved reliability.
    • Removed the legacy test-scripts package and related configuration to reduce maintenance overhead.
    • Simplified ignore settings to reflect current tooling.
  • Tests

    • Migrated test execution to BuildKit, updating package test scripts for consistency and performance.
    • Streamlined test configuration across the workspace.
  • Note

    • No user-facing changes in this release.

@changeset-bot
Copy link

changeset-bot bot commented Aug 26, 2025

🦋 Changeset detected

Latest commit: 58e63b0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@studiocms/web-vitals Patch

Not sure what this means? Click here to learn what changesets are.

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 26, 2025

📝 Walkthrough

Walkthrough

Removes the internal test-scripts package and tooling references, updates root dev dependencies (switching to BuildKit), adjusts ignore/config settings, adds a changeset, and updates the web-vitals package test script to use BuildKit.

Changes

Cohort / File(s) Summary
Repo config updates
\.changeset/config.json, knip.config.ts, package.json
Adjust changeset ignore list (remove test-scripts), remove packages/test-scripts workspace from Knip, bump @withstudiocms/buildkit (0.1.0-beta.1 → 0.1.0-beta.4), remove test-scripts devDependency.
Remove test-scripts package
packages/test-scripts/package.json, packages/test-scripts/index.js, packages/test-scripts/cmd/test.js, packages/test-scripts/jsconfig.json
Delete the test-scripts package, its CLI entrypoint, command implementation, and jsconfig.
Changeset entry
.changeset/little-trees-heal.md
Add a changeset documenting a patch for @studiocms/web-vitals and notes about BuildKit/test scripts.
Web-vitals test script
packages/web-vitals/package.json
Update scripts.test to run buildkit test --timeout 50000 "test/**/*.test.js" instead of test-scripts.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant Dev as Developer
  participant NPM as npm/yarn
  participant PKG as packages/web-vitals
  participant BK as BuildKit (CLI)

  Dev->>NPM: run "npm test" in web-vitals
  NPM->>PKG: execute scripts.test
  Note over PKG: Updated command
  PKG->>BK: buildkit test --timeout 50000 "test/**/*.test.js"
  BK-->>Dev: Test results (spec output, exit code)
Loading
sequenceDiagram
  autonumber
  participant Dev as Developer
  participant NPM as npm/yarn
  participant PKG as packages/web-vitals
  participant TS as test-scripts (removed)
  participant Node as node:test

  rect rgba(240,240,255,0.6)
  Note over TS,Node: Previous flow (removed)
  Dev->>NPM: npm test
  NPM->>PKG: scripts.test
  PKG->>TS: test-scripts test ...
  TS->>Node: Orchestrate node:test, reporters, teardown
  Node-->>Dev: Results
  end
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

Suggested labels

ci

Suggested reviewers

  • louisescher
  • dreyfus92
  • RATIU5

Poem

A bunny taps the build drum light,
Hops past scripts into the night.
Test burrows shift—no CLI maze,
BuildKit beams with quicker rays.
Leaves rustle where old paths slept—
Carrots count the green commits kept. 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-build-kit

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Aug 26, 2025

Open in StackBlitz

npm i https://pkg.pr.new/withstudiocms/web-vitals/@studiocms/web-vitals@36

commit: 58e63b0

@Adammatthiesen Adammatthiesen marked this pull request as ready for review August 26, 2025 00:19
@Adammatthiesen Adammatthiesen requested a review from a team as a code owner August 26, 2025 00:19
@coderabbitai coderabbitai bot added the ci label Aug 26, 2025
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.changeset/little-trees-heal.md (1)

1-5: Clarify the changeset summary with specifics (tool version + package removal).

Calling out the exact BuildKit version and the removal of the test-scripts package will make the changelog more actionable for consumers skimming releases.

Proposed tweak:

 ---
 "@studiocms/web-vitals": patch
 ---
 
-Updated buildkit and test scripts
+Update BuildKit to 0.1.0-beta.4 and migrate tests from internal test-scripts to BuildKit
packages/web-vitals/package.json (1)

49-52: Test runner migration validated; BuildKit flags and glob behavior confirmed

All checks look good:

  • BuildKit v0.1.0-beta.4 supports the test command with --timeout (interpreted in milliseconds) and handles quoted glob patterns internally.
  • The workspace’s root package.json already pins "@withstudiocms/buildkit": "0.1.0-beta.4", but packages/web-vitals/package.json does not list it. If you ever run this package outside the monorepo, consider adding it locally to ensure the binary is always resolvable.

Optional refactor (only if self-containment is desired):

--- a/packages/web-vitals/package.json
+++ b/packages/web-vitals/package.json
@@ "devDependencies": {
+    "@withstudiocms/buildkit": "0.1.0-beta.4",
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 824c14d and 58e63b0.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (9)
  • .changeset/config.json (1 hunks)
  • .changeset/little-trees-heal.md (1 hunks)
  • knip.config.ts (0 hunks)
  • package.json (1 hunks)
  • packages/test-scripts/cmd/test.js (0 hunks)
  • packages/test-scripts/index.js (0 hunks)
  • packages/test-scripts/jsconfig.json (0 hunks)
  • packages/test-scripts/package.json (0 hunks)
  • packages/web-vitals/package.json (1 hunks)
💤 Files with no reviewable changes (5)
  • packages/test-scripts/jsconfig.json
  • knip.config.ts
  • packages/test-scripts/package.json
  • packages/test-scripts/cmd/test.js
  • packages/test-scripts/index.js
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-20T05:47:47.058Z
Learnt from: Adammatthiesen
PR: withstudiocms/web-vitals#8
File: packages/web-vitals/package.json:24-43
Timestamp: 2025-07-20T05:47:47.058Z
Learning: When reviewing package.json exports fields, check for build scripts that generate dist/ artifacts. It's normal for packages to reference build-generated files in exports that aren't committed to the repository, as they're created during the build/publish process.

Applied to files:

  • package.json
🔇 Additional comments (2)
.changeset/config.json (1)

10-10: LGTM: ignore list updated correctly after removing test-scripts.

Removing "test-scripts" from the ignore array is consistent with the package deletion. No other config adjustments needed.

package.json (1)

24-34: All internal runner references removed and BuildKit updated consistently

  • No occurrences of test-scripts remain anywhere in the repo.
  • No npm/yarn/pnpm scripts invoke test-scripts.
  • Only one version of @withstudiocms/buildkit (0.1.0-beta.4) is referenced in package.json.
  • CI workflows under .github/ contain no stale test-runner calls.

@Adammatthiesen Adammatthiesen merged commit de51086 into main Aug 26, 2025
13 checks passed
@Adammatthiesen Adammatthiesen deleted the update-build-kit branch August 26, 2025 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants