Skip to content

fix(studio): restore production build and browser launcher - #76

Draft
zedarvates wants to merge 4 commits into
fix/studio-contract-recoveryfrom
fix/studio-renderer-contracts
Draft

zedarvates wants to merge 4 commits into
fix/studio-contract-recoveryfrom
fix/studio-renderer-contracts

Conversation

@zedarvates

@zedarvates zedarvates commented Oct 3, 2026 •

Copy link
Copy Markdown
Owner

Creative Studio could not build in an isolated install and then rendered a blank browser launcher because forced feature/vendor chunks introduced an initialization cycle. Restore the production build and launcher by rejecting the unshipped demo addon's activation, using the case-correct stylesheet, declaring the direct Ant Design/DnD dependencies, disabling debugger exports whose redaction helper is absent, and letting Rollup preserve its module graph.

Declare the optional renderer Electron bridge and compatibility alias, match the main preload's core shape, and use the actual store Project type. Unknown IPC payloads and optional entity adapters stay explicit. Existing locked package versions and platform/optional entries are retained.

Draft stacked on #75 at 02990d8e0211a5a848bedd499d25f07788c4f3fa; partial repair for #74.

Current-head validation: Renderer CI succeeds on 09bbd0503eb82de4c84f5a7a60801d0d390b40ee. Node 22.12.0 and 24.19.0 both pass isolated installation, two strict compile-only bridge contract programs, ten focused tests and the production bundle. The Node 24.19.0 job also passes a fresh Chromium launcher check without an Electron preload or live providers. Earlier missing-antd and chunk-order failures are recovered on this head. The startup test now unambiguously targets the main creation control.

An isolated local source-patch combination with exact #70 99feb3319e35a896bbdb4505a02a9fa452380329, #63 ca5b890a4fe010065a76294506abbde0b293ec3c and #73 3a8cac25a11ed207192d443562f899cecb54aede also passes installation, both contract programs, ten tests and the updated production bundle using Axios 1.20.0, Undici 7.30.0 and Electron 41.10.6. The hosted checks above cover this PR's own locks, not a merged dependency combination; no Chromium/Electron runtime result is claimed for that combination.

Remaining gaps: full tsc -b fails with 1,623 diagnostics in the local repository setup (2,147 on main), and 1,618 in the isolated dependency combination. Full compiler settings/inclusions are unchanged. Large chunks and performance remain unverified. The bounded browser check does not exercise project creation, Electron IPC, editing, playback or generation. No SonarCloud check/report or commit-status context is exposed on this head through GitHub; #75's passed gate does not cover these changes or prove all security alerts closed.

Review the bridge/extensions, unavailable-addon behavior, deliberate debugger limitation and dependency lock additions. #74 remains open; no merge approval or commercial publication is implied. Scope, commands and remaining acceptance.

@sonarqubecloud

sonarqubecloud Bot commented Oct 3, 2026

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@zedarvates zedarvates changed the title fix(studio): recover renderer bundle and optional Electron contract fix(studio): restore production build and browser launcher Oct 3, 2026
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.

1 participant