Repository navigation
test(QA-03): verify shared compiler targets against CPython - #36
Merged
Merged
Conversation
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.
Closes #25.
The compiler now checks a shared, versioned corpus under isolated CPython and as identical emitted modules in Node and a real browser worker. It compares 24 supported cases for typed results, output order, error classes/messages/original spans and mapped source frames, plus 10 explicit rejected/deferred boundaries. Native JavaScript API observations are recorded separately, and the compatibility matrix describes profile limits.
CI pins CPython 3.14.7 and Node 24.19.0, retains the actual Chromium version and both parity/host reports, and runs the Node/reference gate against installed wheel and source distributions on all three platforms. Borrowed text-metrics artifacts and the runnable browser example retain Shimify's exact MIT notice. The example writer supports the notice subdirectory and rolls it back on failure.
Validation: 82 local tests; 24/24 Node and Chrome 152.0.7977.76 parity cases, 10/10 diagnostic boundaries, 13 real browser-host lifecycle/Fetch/cancellation checks; wheel and sdist build plus isolated installed-wheel conformance.
Depends on #35 for preconstructed exception source origins. Full Python traceback objects, broader Python syntax and runtime source parsing remain separate roadmap tasks. No package was released.