Repository navigation
docs: install and build the client with bun - #160
Conversation
The client now uses bun as its only package manager (Deploy-Center-Client #2), so the FAQ, the v2 to v3 migration guide, the GitHub setup example and the staging checklist install with a frozen bun lockfile. Signed-off-by: Sabry Dawood <kazouya25@gmail.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Caution Review failedThe pull request is closed. Walkthrough
Merge Risk:
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
📋 Description
The client now uses bun as its only package manager (FutureSolutionDev/Deploy-Center-Client#2). This updates the server docs that still told people to install the client with npm:
docs/FAQ.mdanddocs/migration-v2-to-v3.md:bun install --frozen-lockfileandbun run build.docs/guides/GITHUB_SETUP.md: the example client CI job usesoven-sh/setup-bun, and runs install, test and lint with bun.docs/v3.0-staging-verification.md: the client coverage command.🏷️ Type of Change
🧪 How Has This Been Tested?
Docs only. The commands match the client's new CI workflow, which passed on Client #2.
Summary by CodeRabbit