feat: publish v2.0.0

[tclxshunquan-wang]

Summary by CodeRabbit

• Chores

  • Updated dependencies across the project for improved compatibility and performance.
  • Added workspace configuration to enable multi-package workspace resolution.

• Release

  • Published v2.0.0 with major version updates across multiple packages.

[coderabbitai]

Walkthrough

Adds a changeset declaring major (v2.0.0) releases for multiple @hyperse packages and updates project workspace configuration by adding package globs to .yarnrc.yml.

Changes

Cohort / File(s)	Summary
Release Changeset .changeset/lemon-words-hug.md	Declares major version bumps (v2.0.0) for @hyperse/inspector-babel-plugin, @hyperse/inspector-middleware, @hyperse/inspector-component, @hyperse/inspector-swc-plugin, @hyperse/inspector-common, @hyperse/next-inspector, and @hyperse/inspector. Includes a feat entry for publishing v2.0.0 and a chore entry noting cross-project dependency updates.
Yarn Workspace Config .yarnrc.yml	Adds workspace package globs packages/* and crates/* under workspaces.packages, preserving existing nodeLinker and yarnPath settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Review focus: verify the changeset's package list and version intent, ensure workspace globs match repository layout, and confirm no unintended overrides to yarn settings.
• Files meriting extra attention:
  • .changeset/lemon-words-hug.md — confirm package names and semantic intent (major bumps).
  • .yarnrc.yml — ensure workspace globs and existing settings coexist as intended.

Possibly related PRs

• chore: update dependencies in Cargo.toml and package.json for improved compatibility and performance #38 — Modifies dependency versions for SWC-related packages and touches inspector-swc-plugin, likely overlapping with the changeset’s dependency updates.

Poem

🐰 I hopped through changes, pen in paw,
Seven packages marked with a major law.
Workspaces named, versions set to go,
A tiny hop for code, a larger show. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: publish v2.0.0' directly matches the primary change documented in the changeset, which marks a major version release (v2.0.0) for multiple packages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.changeset/lemon-words-hug.md (1)

10-12: Consider consolidating the changelog entries.

The changeset contains two separate entries (feat and chore) on consecutive lines without separating blank lines between them. For clarity and readability in the final changelog, consider combining these into a single entry or adding appropriate separation.

Additionally, the chore entry ends with a semicolon, which is inconsistent with typical changelog formatting (the feat entry has none). Remove the trailing semicolon for consistency.

 ---
 "@hyperse/inspector-babel-plugin": major
 "@hyperse/inspector-middleware": major
 "@hyperse/inspector-component": major
 "@hyperse/inspector-swc-plugin": major
 "@hyperse/inspector-common": major
 "@hyperse/next-inspector": major
 "@hyperse/inspector": major
 ---
 
 feat: publish v2.0.0
-chore: update dependencies across the project for improved compatibility and performance;
+chore: update dependencies across the project for improved compatibility and performance

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3b94960 and ab8b97a.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (1)

• .changeset/lemon-words-hug.md (1 hunks)

🔇 Additional comments (1)

.changeset/lemon-words-hug.md (1)

1-9: Verify package list completeness against v2.0.0 release scope.

The AI summary mentions eight packages with major version bumps, but only seven are listed in the changeset (the summary may be inaccurate). Confirm this is intentional and that all packages intended for v2.0.0 are included. If an eighth package was meant to be part of this release, add it to maintain consistency.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ab8b97a and f310ff5.

📒 Files selected for processing (1)

• .yarnrc.yml (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: github pages

.yarnrc.yml

[error] 1-1: Usage Error: Unrecognized or legacy configuration settings found: workspaces. Run 'yarn config' to see the list of settings supported in Yarn. Command 'yarn install' failed with exit code 1.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Invalid workspace configuration for Yarn 4.x — pipeline is failing.

The workspaces key is not a recognized configuration setting in Yarn 4.10.3 (as indicated by the pipeline failure). In Yarn v2+, workspaces are defined in package.json, not .yarnrc.yml.

After confirming the correct syntax, move the workspace configuration from .yarnrc.yml to package.json. For reference, the pipeline error was:

[error] 1-1: Usage Error: Unrecognized or legacy configuration settings found: workspaces. Run 'yarn config' to see the list of settings supported in Yarn. Command 'yarn install' failed with exit code 1.

---

🌐 Web query:

How to configure Yarn v4 workspaces in package.json?

💡 Result:

Short answer — in Yarn v4 you declare workspaces in the root package.json with a workspaces field (glob patterns), make the root private, optionally set packageManager, and use the workspace: protocol in workspace-to-workspace dependencies. Example:

Root package.json
{
"private": true,
"packageManager": "[email protected]",
"workspaces": [
"packages/",
"apps/"
]
}

Workspace package (packages/pkg-a/package.json)
{
"name": "@myorg/pkg-a",
"version": "1.0.0",
"main": "dist/index.js",
"dependencies": {
"lodash": "^4.17.21"
}
}

Workspace package that depends on another workspace (packages/pkg-b/package.json)
{
"name": "@myorg/pkg-b",
"version": "1.0.0",
"dependencies": {
"@myorg/pkg-a": "workspace:*"
}
}

Notes:

• workspaces can be an array of glob patterns (root manifest). [1]
• Use "workspace:*", "workspace:^", etc. to reference local workspace versions and keep resolution consistent. You can still run yarn workspaces foreach, yarn workspace , and use yarn workspaces focus to limit installs. [1][2][3]

References:
[1] Yarn manifest (package.json) — workspaces docs.
[2] Yarn workspaces feature page.
[3] Yarn protocols (workspace: protocol examples).

---

Move workspace configuration from .yarnrc.yml to package.json.

The workspaces key is not supported in .yarnrc.yml for Yarn 4.x. In Yarn v4, workspaces must be defined in the root package.json as an array. Move lines 3-6 to your root package.json:

{
  "private": true,
  "workspaces": [
    "packages/*",
    "crates/*"
  ]
}

Then remove the workspace configuration from .yarnrc.yml.

🤖 Prompt for AI Agents

.yarnrc.yml around lines 3-6: the workspace configuration belongs in the root
package.json for Yarn v4, so remove the workspaces section from .yarnrc.yml and
add a "private": true and "workspaces": ["packages/*","crates/*"] entry to the
root package.json (as an array), ensuring the workspaces entries are moved
exactly and formatted as a JSON array under package.json, then save both files.