chore: fix lockfile

[dyc3]

Summary

should fix the website sync failure

[netlify]

✅ Deploy Preview for biomejs ready!

Name	Link
🔨 Latest commit	8c2ea80
🔍 Latest deploy log	https://app.netlify.com/projects/biomejs/deploys/69593ffd31b4860008f0ce37
😎 Deploy Preview	https://deploy-preview-3777--biomejs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Walkthrough

The package.json file has been updated to point the "@biomejs/wasm-web" devDependency to a new URL with a different commit hash. This is a minor version update of an existing dependency with no alterations to other dependencies, scripts, or the overall project structure. No functional changes or new exported entities are introduced.

Pre-merge checks

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: fix lockfile' directly relates to the changeset which updates a devDependency URL in package.json, addressing lockfile synchronisation.
Description check	✅ Passed	The description mentions fixing a website sync failure, which aligns with the lockfile update intended to resolve synchronisation issues.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e7efffd and 8c2ea80.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: Redirect rules - biomejs
• GitHub Check: Header rules - biomejs
• GitHub Check: Pages changed - biomejs
• GitHub Check: test
• GitHub Check: Generate Lunaria Overview

🔇 Additional comments (2)

package.json (2)

37-37: Query: Is pkg.pr.new appropriate for main branch?

The updated dependency uses a temporary PR package preview URL. Whilst this works as a quick fix, it's unusual for production code on main—such URLs are ephemeral and can become unavailable. Is this a permanent fix, or should a stable npm release from biomejs/biome eventually replace it?

---

27-86: Verify lockfile regeneration.

The pnpm lockfile (pnpm-lock.yaml) was not provided for review. Please confirm that you've regenerated it with pnpm install and committed the updated lockfile alongside this change. Also, a bit more context in the PR description about which sync failure this resolves would be helpful for future maintainers.

---

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