chore(dependencies): update dependencies to use catalog references

[christophe-g]

• Changed dependencies in multiple package.json files to use catalog references instead of specific versions.
• Updated the pnpm-workspace.yaml to include new catalog entries for effect and firebase packages.

Summary by CodeRabbit

• Chores
  • Switched project to a centralized version catalog for multiple dependencies, unifying version references across packages and examples.
  • Updated workspace configuration and package metadata to reference the catalog and adjusted workspace formatting.
  • Added catalog entries and build/ignore lists to streamline dependency management and packaging.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7ad80150-966a-444f-b1c2-ef923197ad55

📥 Commits

Reviewing files that changed from the base of the PR and between c47118f and 2516a96.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• example/shared/package.json
• pnpm-workspace.yaml

---

📝 Walkthrough

Walkthrough

Centralizes dependency versions in pnpm-workspace.yaml's catalog and updates root, workspace packages, and example package.json files to reference those versions via catalog: specifiers; also reformats workspace globs and build allowlists.

Changes

Dependency version catalog migration

Layer / File(s)	Summary
Workspace catalog configuration pnpm-workspace.yaml	Introduces a catalog section defining versions for effect, @effect/*, Firebase packages, and others; reforms workspace glob quoting and updates ignoredBuiltDependencies / onlyBuiltDependencies.
Workspace packages catalog adoption packages/admin/package.json, packages/client/package.json, packages/effect-firebase/package.json, packages/mock/package.json	Workspace packages change dependencies, devDependencies, and peerDependencies to use catalog: specifiers (keeping workspace:* for internal links and preserving publishConfig).
Root and example applications catalog adoption package.json, example/app/package.json, example/backend/package.json, example/shared/package.json	Root and example package.json files update dependency entries to catalog: references and include minor end-of-file/formatting adjustments.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• fwal/effect-firebase#31: Also modifies effect and related @effect/* dependency entries across package.json files.

Poem

I’m a rabbit with a catalog cart,
Gathering versions, doing my part,
One pnpm list to rule the fray,
Semver scattered now tucked away,
Happy builds — hop, hop, restart! 🐇📦

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main objective of the changeset - updating dependencies across multiple package.json files and pnpm-workspace.yaml to use catalog references for version management.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.}

[christophe-g]

This is to ease version sync with other libraries using effect-firebase

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pnpm-workspace.yaml`:
- Around line 7-9: The YAML entries are using inconsistent quoting for package
keys/values (see "`@effect/vitest`", "`@effect/platform-browser`", and effect); make
the style consistent by either adding quotes around the unquoted identifier
(change effect: 4.0.0-beta.78 to "effect": "4.0.0-beta.78") or removing quotes
from the quoted entries so all three follow the same format; update the entries
for "`@effect/vitest`", "`@effect/platform-browser`", and effect accordingly.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e7e87e3a-ddd0-4a44-8805-68790bd6f220

📥 Commits

Reviewing files that changed from the base of the PR and between 36a08a4 and c47118f.

📒 Files selected for processing (8)

• example/app/package.json
• example/backend/package.json
• package.json
• packages/admin/package.json
• packages/client/package.json
• packages/effect-firebase/package.json
• packages/mock/package.json
• pnpm-workspace.yaml