Make Studio Code aware of theme asset bundling - #4262
Merged
Conversation
sejas
approved these changes
Jul 21, 2026
sejas
left a comment
Member
There was a problem hiding this comment.
LGTM. I confirmed there is no regression in child themes eval by running npm run eval -- --filter-pattern "child theme"
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.
Related issues
How AI was used in this PR
I used Claude to investigate Studio Code's existing theme guardrails, confirm the asset-bundling gap, and draft the guardrail wording. I reviewed and validated the wording and the design decision (awareness over auto-running builds) myself.
Proposed Changes
A user customizing a site on an installed theme reported that Studio Code edited the theme's
style.cssdirectly. The existing guardrail already routes design changes into a child theme, but its reasoning only mentioned that a theme update wipes such edits. It missed a second failure mode: many themes serve a compiled or minified stylesheet in production (for examplestyle.min.css, or assets built intobuild/ordist/) while the readable source loads only in development, so an edit to the source may never reach the rendered site, and Studio has no build step to recompile it.Testing Instructions
Pre-merge Checklist