Skip to content

fix(core): allow project arrays in framework build options - #25534

Draft
nicohrubec wants to merge 1 commit into
developfrom
feat/framework-project-arrays
Draft

nicohrubec wants to merge 1 commit into
developfrom
feat/framework-project-arrays

Conversation

@nicohrubec

Copy link
Copy Markdown
Member

Framework build options reject project arrays that the bundler plugins already support. Widen the shared option and handle React Router's single-project CLI clients by associating releases with all configured projects and uploading through one client per project. Debug IDs are injected once, and source maps are preserved if an upload fails.

Adds focused coverage for multi-project uploads, cleanup ordering/failures, empty arrays, omitted projects, and array-valued framework configurations.

Fixes #21069

React Router's build, lint, and all 268 tests pass; the focused type fixtures and the Nuxt, SvelteKit, SolidStart, Remix, Nitro, and TanStack Start suites also pass. Broader local checks encounter existing install/build issues: missing pnpm metadata, outdated conventions exports and Node declarations, and no current SDK tarballs for E2E tests.

Co-Authored-By: GPT-6 <codex@openai.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

project option should accept string | string[] across all framework SDKs

1 participant