[Blueprints] Add Blueprint execution compile facade - #3899
Closed
adamziel wants to merge 1 commit into
Closed
Conversation
adamziel
force-pushed
the
reject-v2-runtime-php-unsatisfied
branch
from
July 3, 2026 14:01
4de7b06 to
c0f452b
Compare
adamziel
force-pushed
the
add-blueprint-execution-compile-facade
branch
from
July 3, 2026 14:02
3537be2 to
0f75a2a
Compare
adamziel
added a commit
that referenced
this pull request
Jul 3, 2026
## What Adds `compileBlueprintForExecution()` as a small v1-only facade that returns the compiled Blueprint together with the normalized declaration and `run` function. ## Why Consumers that need to support multiple Blueprint execution paths need an entrypoint shaped around execution, not the legacy v1-only `compileBlueprint()` alias. This introduces the public shape without adding Blueprint v2 compiler behavior yet. Replaces #3899, which was closed when the lower stacked base branch was deleted after #3898 merged. ## Testing - `npm run format:uncommitted` - `npm exec nx run playground-blueprints:test:vite -- --testFiles=packages/playground/blueprints/src/tests/compile.spec.ts` - `npm exec nx run playground-blueprints:typecheck` - `npm exec nx run playground-blueprints:lint` - `git diff --check`
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
Adds
compileBlueprintForExecution()as a small v1-only facade that returns the compiled Blueprint together with the normalized declaration andrunfunction.Why
Consumers that need to support multiple Blueprint execution paths need an entrypoint shaped around execution, not the legacy v1-only
compileBlueprint()alias. This introduces the public shape without adding Blueprint v2 compiler behavior yet.Testing
npm run format:uncommittednpm exec nx run playground-blueprints:test:vite -- --testFiles=packages/playground/blueprints/src/tests/compile.spec.tsnpm exec nx run playground-blueprints:typechecknpm exec nx run playground-blueprints:lintgit diff --check