chore(deps): enroll 47 third-party packages into Bun workspace catalog#2416
Merged
Conversation
Contributor
WalkthroughThis PR converts 47 third-party packages from pinned versions to a centralized Bun workspace ChangesCatalog System Enrollment
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labelsci/cd Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsStopped waiting for pipeline failures after 30000ms. One of your pipelines takes longer than our 30000ms fetch window to run, so review may not consider pipeline-failure results for inline comments if any failures occurred after the fetch window. Increase the timeout if you want to wait longer or run a 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. Comment |
github-actions
Bot
added
documentation
Contributor
Coverage Report for Expo Unit Tests Coverage (./apps/expo)
File CoverageNo changed files found. |
Contributor
Coverage Report for API Unit Tests Coverage (./packages/api)
File CoverageNo changed files found. |
Contributor
Deploying packrat-landing with
|
| Latest commit: |
b2fe566
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://05c3f720.packrat-landing.pages.dev |
| Branch Preview URL: | https://chore-enroll-catalog-candida.packrat-landing.pages.dev |
Contributor
Deploying packrat-guides with
|
| Latest commit: |
b2fe566
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3d08e3aa.packrat-guides-6gq.pages.dev |
| Branch Preview URL: | https://chore-enroll-catalog-candida.packrat-guides-6gq.pages.dev |
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
packrat-admin | b2fe566 | Commit Preview URL Branch Preview URL |
May 14 2026, 02:27 PM |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR centralizes shared third-party dependency versions by enrolling additional “catalog candidate” packages into Bun’s root workspace catalog, replacing repeated pinned versions across multiple workspace package.json files with "catalog:" to prevent version drift.
Changes:
- Expanded the root
package.json"catalog"with additional shared third-party dependencies. - Updated multiple workspace manifests to reference shared versions via
"catalog:"instead of explicit version strings. - Regenerated
bun.lockand added a planning doc describing the enrollment process and acceptance criteria.
Reviewed changes
Copilot reviewed 18 out of 19 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| packages/web-ui/package.json | Switches shared UI deps (and some peers/dev deps) to "catalog:" references. |
| packages/units/package.json | Moves vitest to "catalog:" for shared test tooling consistency. |
| packages/overpass/package.json | Moves vitest to "catalog:" for shared test tooling consistency. |
| packages/osm-import/package.json | Moves pg to "catalog:" to centralize DB driver versioning. |
| packages/osm-db/package.json | Moves DB/runtime deps (pg, ws, drizzle, neon) to "catalog:" and catalogs drizzle-kit. |
| packages/mcp/package.json | Switches shared Cloudflare/vitest/wrangler deps to "catalog:". |
| packages/cli/package.json | Switches shared deps (e.g., @duckdb/node-api, consola, @types/bun) to "catalog:". |
| packages/app/package.json | Moves shared state/query deps to "catalog:" (deps + peers). |
| packages/api/package.json | Moves shared infra deps (@neondatabase/serverless, pg, ws, vitest tooling, etc.) to "catalog:". |
| packages/analytics/package.json | Switches shared deps and test tooling to "catalog:". |
| package.json | Adds new catalog entries for shared third-party deps (now used across workspaces). |
| docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md | Documents the catalog enrollment plan, rationale, and acceptance criteria. |
| bun.lock | Updates lockfile to reflect catalog-based dependency specs and resolved versions. |
| apps/web/package.json | Switches shared web app deps (next, query tooling, styles tooling) to "catalog:". |
| apps/trails/package.json | Switches shared trails app deps (Next/UI/map deps + dev tooling) to "catalog:". |
| apps/landing/package.json | Switches shared landing app deps (form/UI/style tooling) to "catalog:". |
| apps/guides/package.json | Switches shared guides app deps (AI SDK, UI tooling, style tooling) to "catalog:". |
| apps/expo/package.json | Switches shared Expo deps and test tooling to "catalog:". |
| apps/admin/package.json | Switches shared admin app deps (Next/UI/map deps + dev tooling) to "catalog:". |
Comments suppressed due to low confidence (1)
docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md:59
@types/bunis listed with versionlatest, which is not a pinned version and can change over time. To keep installs deterministic and align with the catalog’s purpose, consider replacinglatestwith a specific version (matching what bun.lock resolved).
| `@tanstack/react-query` | `^5.70.0` | apps/web, apps/admin, apps/expo, apps/guides, packages/app |
| `@tanstack/react-query-devtools` | `^5.70.0` | apps/web, apps/guides |
| `@types/bun` | `latest` | packages/cli, packages/api, packages/analytics |
| `@types/leaflet` | `^1.9.21` | apps/trails, apps/admin, apps/expo |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "@radix-ui/react-tooltip": "^1.2.7", | ||
| "@tanstack/react-query": "^5.70.0", | ||
| "@tanstack/react-query-devtools": "^5.70.0", | ||
| "@types/bun": "latest", |
Comment on lines
+43
to
+44
| All 47 are currently at a **consistent version** across all workspaces (no mismatches), so the | ||
| catalog version is simply the existing pinned string. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
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 `@docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md`:
- Around line 29-36: The markdown in
docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md has fenced JSON
blocks that lack surrounding blank lines which triggers markdownlint MD031; add
a blank line before and after each fenced code block (the block containing
"package-name": "^x.y.z" and the block containing "package-name": "catalog:") so
each fenced ```json ... ``` is separated by an empty line from the surrounding
list items and paragraphs.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: c41c41b4-8203-4d78-a0c8-34ff1a3cbabf
⛔ Files ignored due to path filters (2)
apps/guides/bun.lockis excluded by!**/*.lockbun.lockis excluded by!**/*.lock,!bun.lock
📒 Files selected for processing (19)
.github/scripts/configure-deps.tsapps/admin/package.jsonapps/expo/package.jsonapps/guides/package.jsonapps/landing/package.jsonapps/trails/package.jsonapps/web/package.jsondocs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.mdpackage.jsonpackages/analytics/package.jsonpackages/api/package.jsonpackages/app/package.jsonpackages/cli/package.jsonpackages/mcp/package.jsonpackages/osm-db/package.jsonpackages/osm-import/package.jsonpackages/overpass/package.jsonpackages/units/package.jsonpackages/web-ui/package.json
Comment on lines
+29
to
+36
| 1. Add an entry to the `"catalog"` object in root `package.json`: | ||
| ```json | ||
| "package-name": "^x.y.z" | ||
| ``` | ||
| 2. In every workspace `package.json` that pins that dep, replace the explicit version with: | ||
| ```json | ||
| "package-name": "catalog:" | ||
| ``` |
Contributor
There was a problem hiding this comment.
Add blank lines around fenced JSON blocks to clear markdownlint MD031.
Lines 30–32 and 34–36 need surrounding blank lines; otherwise docs lint can fail.
Suggested fix
1. Add an entry to the `"catalog"` object in root `package.json`:
+
```json
"package-name": "^x.y.z"
```
+
2. In every workspace `package.json` that pins that dep, replace the explicit version with:
+
```json
"package-name": "catalog:"
```📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| 1. Add an entry to the `"catalog"` object in root `package.json`: | |
| ```json | |
| "package-name": "^x.y.z" | |
| ``` | |
| 2. In every workspace `package.json` that pins that dep, replace the explicit version with: | |
| ```json | |
| "package-name": "catalog:" | |
| ``` | |
| 1. Add an entry to the `"catalog"` object in root `package.json`: |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 30-30: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
[warning] 32-32: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
[warning] 34-34: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
🤖 Prompt for 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.
In `@docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md` around lines
29 - 36, The markdown in
docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md has fenced JSON
blocks that lack surrounding blank lines which triggers markdownlint MD031; add
a blank line before and after each fenced code block (the block containing
"package-name": "^x.y.z" and the block containing "package-name": "catalog:") so
each fenced ```json ... ``` is separated by an empty line from the surrounding
list items and paragraphs.
Move all CATALOG CANDIDATE dependencies (same version pinned in 2+ workspaces) into the root catalog section. Replace pinned version strings with "catalog:" in 16 workspace package.json files (164 replacements total). Root catalog grows from 46 → 93 entries. The no-duplicate-deps pre-push check now shows 0 third-party candidates; only workspace:* internal refs remain (intentional — they use the workspace protocol, not semver).
…atalog resolution
apps/guides/bun.lock was created in isolation ('my-v0-project') and didn't
understand catalog: entries from the monorepo root. CF Pages found this file
and tried to install against it, failing to resolve the new catalog: deps.
Deleting it lets CF Pages use the root bun.lock like all other apps.
…ges token When packrat-guides builds on Cloudflare Pages and PACKRAT_NATIVEWIND_UI_GITHUB_TOKEN is absent, the preinstall hook now prints the exact CF Pages dashboard path to add it, rather than the generic CI secrets message. Root cause of packrat-guides CF Pages failure since c29d174: the token was removed or expired in the CF Pages project environment variables. Fix: add PACKRAT_NATIVEWIND_UI_GITHUB_TOKEN (GitHub PAT with read:packages scope) to the packrat-guides CF Pages project settings. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
…uides Pre-push hook caught that apps/landing and apps/guides were pinning vitest@~3.1.4 directly instead of referencing the workspace catalog entry.
andrew-bierman
force-pushed
the
chore/enroll-catalog-candidates
branch
from
7871c15 to
b2fe566
Compare
Cloudflare Workers enforces a hard cap of 300,000 ms (code: 10206). The previous value of 400,000 ms caused every wrangler deploy to fail. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
♻️ Duplicate comments (1)
docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md (1)
29-36:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winAdd blank lines around fenced JSON blocks to clear markdownlint MD031.
The fenced code blocks at lines 30–32 and 34–36 still need surrounding blank lines to satisfy MD031.
📝 Proposed fix
1. Add an entry to the `"catalog"` object in root `package.json`: + ```json "package-name": "^x.y.z" ``` + 2. In every workspace `package.json` that pins that dep, replace the explicit version with: + ```json "package-name": "catalog:" ```🤖 Prompt for 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. In `@docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md` around lines 29 - 36, The Markdown fenced JSON blocks containing `"package-name": "^x.y.z"` and `"package-name": "catalog:"` lack blank lines before and after which triggers markdownlint MD031; edit the document to insert a blank line above the opening ```json fence and a blank line below the closing ``` fence for both fenced blocks so each code block is separated from surrounding text (preserve the exact code inside the fences).
🤖 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 @.github/scripts/configure-deps.ts:
- Line 58: The hardcoded Cloudflare Pages project name "packrat-guides" in the
string on configure-deps.ts should be made generic or dynamic: update the array
entry that currently contains ' dash.cloudflare.com → Pages → packrat-guides →
Settings → Environment variables' to either a generic path like '
dash.cloudflare.com → Pages → <project> → Settings → Environment variables' or
construct it with the CF_PAGES_PROJECT_NAME env var (e.g. use
process.env.CF_PAGES_PROJECT_NAME with a sensible fallback) so the navigation
instruction is correct for other apps.
In `@docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md`:
- Line 58: Replace the floating `latest` spec for the dependency `@types/bun`
with the actual resolved version currently used across workspaces (e.g., the
version shown in lockfile or node_modules) and update the dependency entries in
the catalog and the affected package.json files (packages/cli, packages/api,
packages/analytics) to that exact version string; locate the `@types/bun` row in
the catalog table and the dependency entries in each package's package.json (or
the central catalog mechanism you use) and change `latest` to the pinned version
(e.g., "1.2.3") so installs are deterministic.
In `@package.json`:
- Line 81: Update the dependency spec for the `@duckdb/node-api` package to use a
pre-release range operator so minor/patch pre-release updates are allowed;
change the version string for the "@duckdb/node-api" entry in package.json to
use a tilde pre-release range (e.g., ~1.5.0-r.1) if you want to permit
patch-level updates within the 1.5.0-r series, or else add an inline comment
next to the "@duckdb/node-api" key documenting why an exact pin is required for
this native module and leave it as-is.
- Line 120: Replace the non-reproducible version specifier "latest" for the
`@types/bun` dependency in package.json with a pinned range such as "^1.2.17" (or
the exact version you currently have in root devDependencies); open
package.json, locate the dependency key "@types/bun" and change its value from
"latest" to the chosen caret/tilde or exact version string, then run an install
to update the lockfile to ensure deterministic installs.
---
Duplicate comments:
In `@docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md`:
- Around line 29-36: The Markdown fenced JSON blocks containing `"package-name":
"^x.y.z"` and `"package-name": "catalog:"` lack blank lines before and after
which triggers markdownlint MD031; edit the document to insert a blank line
above the opening ```json fence and a blank line below the closing ``` fence for
both fenced blocks so each code block is separated from surrounding text
(preserve the exact code inside the fences).
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: f83aedcb-f4a2-4515-9e8b-d938935f069e
⛔ Files ignored due to path filters (2)
apps/guides/bun.lockis excluded by!**/*.lockbun.lockis excluded by!**/*.lock,!bun.lock
📒 Files selected for processing (19)
.github/scripts/configure-deps.tsapps/admin/package.jsonapps/expo/package.jsonapps/guides/package.jsonapps/landing/package.jsonapps/trails/package.jsonapps/web/package.jsondocs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.mdpackage.jsonpackages/analytics/package.jsonpackages/api/package.jsonpackages/app/package.jsonpackages/cli/package.jsonpackages/mcp/package.jsonpackages/osm-db/package.jsonpackages/osm-import/package.jsonpackages/overpass/package.jsonpackages/units/package.jsonpackages/web-ui/package.json
| console.error(`❌ ${TOKEN_VAR} not found in Cloudflare Pages build environment.`); | ||
| console.error('Add it as an environment variable in the CF Pages project settings:'); | ||
| console.error( | ||
| ' dash.cloudflare.com → Pages → packrat-guides → Settings → Environment variables', |
Contributor
There was a problem hiding this comment.
Hardcoded CF Pages project name may cause confusion.
Line 58 hardcodes "packrat-guides" in the navigation path. If other apps in this monorepo are also deployed to CF Pages, this instruction will be incorrect for those builds.
CF Pages typically provides a CF_PAGES_PROJECT_NAME environment variable. Consider either:
- Dynamically inserting the project name from the environment
- Making the path generic without a specific project name
📝 Proposed fix to make the path generic
- console.error(
- ' dash.cloudflare.com → Pages → packrat-guides → Settings → Environment variables',
- );
+ console.error(
+ ' dash.cloudflare.com → Pages → [your-project] → Settings → Environment variables',
+ );Or with dynamic project name:
console.error('Add it as an environment variable in the CF Pages project settings:');
+ const projectName = process.env.CF_PAGES_PROJECT_NAME || '[your-project]';
console.error(
- ' dash.cloudflare.com → Pages → packrat-guides → Settings → Environment variables',
+ ` dash.cloudflare.com → Pages → ${projectName} → Settings → Environment variables`,
);🤖 Prompt for 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.
In @.github/scripts/configure-deps.ts at line 58, The hardcoded Cloudflare Pages
project name "packrat-guides" in the string on configure-deps.ts should be made
generic or dynamic: update the array entry that currently contains '
dash.cloudflare.com → Pages → packrat-guides → Settings → Environment variables'
to either a generic path like ' dash.cloudflare.com → Pages → <project> →
Settings → Environment variables' or construct it with the CF_PAGES_PROJECT_NAME
env var (e.g. use process.env.CF_PAGES_PROJECT_NAME with a sensible fallback) so
the navigation instruction is correct for other apps.
| | `@neondatabase/serverless` | `^1.0.0` | packages/api, packages/osm-db | | ||
| | `@tanstack/react-query` | `^5.70.0` | apps/web, apps/admin, apps/expo, apps/guides, packages/app | | ||
| | `@tanstack/react-query-devtools` | `^5.70.0` | apps/web, apps/guides | | ||
| | `@types/bun` | `latest` | packages/cli, packages/api, packages/analytics | |
Contributor
There was a problem hiding this comment.
Pin @types/bun to a specific version instead of latest.
The catalog's purpose is to ensure version consistency across workspaces. Specifying latest defeats this guarantee because each bun install can resolve to a different version, causing silent drift between environments.
🔧 Suggested fix
Determine the current resolved version of @types/bun across the workspaces and pin it explicitly:
-| `@types/bun` | `latest` | packages/cli, packages/api, packages/analytics |
+| `@types/bun` | `^1.2.3` | packages/cli, packages/api, packages/analytics |Replace ^1.2.3 with the actual version currently in use. If you want to stay on the latest types, manually bump the pinned version when upgrading Bun rather than using the floating latest tag.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| | `@types/bun` | `latest` | packages/cli, packages/api, packages/analytics | | |
| | `@types/bun` | `^1.2.3` | packages/cli, packages/api, packages/analytics | |
🤖 Prompt for 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.
In `@docs/plans/2026-05-13-chore-enroll-catalog-candidates-plan.md` at line 58,
Replace the floating `latest` spec for the dependency `@types/bun` with the
actual resolved version currently used across workspaces (e.g., the version
shown in lockfile or node_modules) and update the dependency entries in the
catalog and the affected package.json files (packages/cli, packages/api,
packages/analytics) to that exact version string; locate the `@types/bun` row in
the catalog table and the dependency entries in each package's package.json (or
the central catalog mechanism you use) and change `latest` to the pinned version
(e.g., "1.2.3") so installs are deterministic.
| "catalog": { | ||
| "@ai-sdk/openai": "^3.0.53", | ||
| "@cloudflare/workers-types": "^4.20250405.0", | ||
| "@duckdb/node-api": "1.5.0-r.1", |
Contributor
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial | 💤 Low value
Consider adding a range operator to the pre-release pin.
@duckdb/node-api is the only catalog entry without a version-range operator (all others use ^ or ~). If you want to allow patch updates within the 1.5.0-r pre-release series, use ~1.5.0-r.1. If you need an exact pin because this is a fragile native module, document that intent in a comment or keep as-is.
🤖 Prompt for 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.
In `@package.json` at line 81, Update the dependency spec for the `@duckdb/node-api`
package to use a pre-release range operator so minor/patch pre-release updates
are allowed; change the version string for the "@duckdb/node-api" entry in
package.json to use a tilde pre-release range (e.g., ~1.5.0-r.1) if you want to
permit patch-level updates within the 1.5.0-r series, or else add an inline
comment next to the "@duckdb/node-api" key documenting why an exact pin is
required for this native module and leave it as-is.
| "@radix-ui/react-tooltip": "^1.2.7", | ||
| "@tanstack/react-query": "^5.70.0", | ||
| "@tanstack/react-query-devtools": "^5.70.0", | ||
| "@types/bun": "latest", |
Contributor
There was a problem hiding this comment.
Replace "latest" with a pinned version range.
Using "latest" for @types/bun makes the lockfile non-reproducible—different installs may resolve different versions. Pin to a specific range (e.g., "^1.2.17" to match your current root devDependency, or use a caret/tilde range if you want updates within bounds).
📌 Proposed fix
- "@types/bun": "latest",
+ "@types/bun": "^1.2.17",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "@types/bun": "latest", | |
| "@types/bun": "^1.2.17", |
🤖 Prompt for 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.
In `@package.json` at line 120, Replace the non-reproducible version specifier
"latest" for the `@types/bun` dependency in package.json with a pinned range such
as "^1.2.17" (or the exact version you currently have in root devDependencies);
open package.json, locate the dependency key "@types/bun" and change its value
from "latest" to the chosen caret/tilde or exact version string, then run an
install to update the lockfile to ensure deterministic installs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apps/guides/bun.lock(my-v0-project) that predated the monorepo and caused CF Pages catalog resolution failuresCloudflare Pages: packrat-guidespreinstall hook error message to show the exact CF Pages dashboard path whenPACKRAT_NATIVEWIND_UI_GITHUB_TOKENis missingCloudflare Pages: packrat-apideploy failure —wrangler.jsonchadcpu_ms: 400000but Cloudflare's hard cap is 300,000 ms (error code 10206)Acceptance criteria
bun ./scripts/lint/no-duplicate-deps.ts→ 0 CATALOG CANDIDATES for third-party packages ✅bun run check-typesexits 0 ✅bun installre-run to sync lockfile ✅Post-Deploy Monitoring & Validation
cpu_mscap change; confirm the API worker deploys without error 10206wrangler deploycompletes; Worker CPU limit shows 300 s in the dashboardlimits.cpu_ms