Repository navigation
consume new compile project endpoint - #11757
Merged
Richard Knoll (riknoll) merged 6 commits intoNov 13, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Critical regressions exclude required native build inputs from requests and hashes, break project include paths and simulator-only compilation, and leave the new CLI tests unable to type-check.
5 open issues
Create cloud request data only for native compilations · New Retain native build configuration files in the project filter · New Preserve the original project name for native include paths · New Align request tests with the implemented API · New Remove projectCompileData when C++ files are not retained · New
What changed in this PR
Updates PXT’s native compilation pipeline to consume the new project-based cloud endpoint, with shared request preparation for compiler and backend use.
Changes:
- Adds canonical native-project payloads and hashes.
- Uses the project compile endpoint, checks both hex cache locations, and fetches the returned build URL.
- Removes support for package-level
npmDependenciesandplatformio, with warnings, documentation, and request-focused tests.
| File | Description |
|---|---|
tests/common/testUtils.ts |
Adds a target version to the shared test fixture. |
tests/cli-test/clirunner.ts |
Adds request, variant, dependency, and legacy-field test cases. |
pxtlib/shared/packageutils.ts |
Removes unsupported package fields with warnings. |
pxtlib/shared/extensionrequest.ts |
Prepares canonical project requests, encoded payloads, and hashes. |
pxtlib/shared/extensioninfo.ts |
Ignores legacy package settings while preserving target-level PlatformIO configuration. |
pxtlib/package.ts |
Attaches project request data during compile-option preparation. |
pxtlib/cpp.ts |
Integrates the project endpoint, cache lookup, and returned build URLs. |
localtypings/pxtpackage.d.ts |
Removes obsolete package configuration fields. |
localtypings/pxtarget.d.ts |
Adds project payload and hash fields to extension metadata. |
docs/extensions/pxt-json.md |
Documents removed fields and supported PlatformIO target settings. |
backendutils/backendutils.ts |
Includes shared request helpers in the backend bundle. |
Review effort: Max
| packageUtils.isVariantDisabled(configs[resolvePath(dep)], variant)); | ||
|
|
||
| const config: PackageConfig = { | ||
| name: path ? original.name : "this", |
Member
Author
There was a problem hiding this comment.
this is technically a breaking change, but one that will only affect extension authors and not end-users. and i think it's pretty unlikely to affect the extension authors either; only if they were prefixing their includes with the name of their extension
Joey Wunderlich (jwunderl)
approved these changes
Nov 13, 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.


consuming the new project endpoint.
also deprecating the old platformio and npmDependencies fields in pxt.json since we don't actually use them anywhere; i think they were mostly just for testing new hardware builds