Add --unsafe flag to app dev - #8258
Draft
dmerand wants to merge 1 commit into
Draft
Conversation
Assisted-By: devx/af011388-1430-43c8-9dd8-5d485440ed55
dmerand
force-pushed
the
dlm-app-dev-unsafe-flag
branch
from
August 6, 2026 16:54
1a6202f to
40c1a87
Compare
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
1 participant
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.
What
Add
--unsafetoshopify app devand pass it to dev-session create/update mutations. When enabled, the platform can bypass validations that block local iteration, such as the Remote DOM bundle size limit.Why
The 64 KB Remote DOM bundle limit blocks partner iteration during development. The platform escape hatch is shipped in shop/world#980602 and #980475.
Smoke test
Run
shopify app dev --unsafewith an app that has a Remote DOM UI extension bundle larger than 64 KB. Confirm the dev session starts and subsequent extension updates use the unsafe option.Merge order
Do not merge until shop/world#980602 and shop/world#980475 are deployed. The mutation documents declare
$unsafe; older servers fail GraphQL validation for all dev sessions, not only unsafe ones.The vendored app-dev schema is gitignored and fetched by CI, so the "Check graphql-codegen has been run" check stays red until the platform PRs merge (CI fetches the schema from shop/world
main, which does not yet defineunsafe). After they merge:pnpm graphql-codegen:get-graphql-schemas && pnpm graphql-codegen, confirm no diff in generated files, and the check goes green. Local development used a hand-patched local schema; it is not committed.