Repository navigation
fix(studio): restore production build and browser launcher - #76
Draft
zedarvates wants to merge 4 commits into
Draft
zedarvates wants to merge 4 commits into
zedarvates wants to merge 4 commits into
Conversation
|
This was referenced Oct 3, 2026
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.




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, #63ca5b890a4fe010065a76294506abbde0b293ec3cand #733a8cac25a11ed207192d443562f899cecb54aedealso 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 -bfails 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.