feat: add @js/ summoned-JavaScript routing -codex - #1
Merged
Merged
Conversation
This branch was successfully deployed
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.
Adds the reserved
@js/<name>routing class for summoned JavaScript. Imports now resolve underjs_modules/<name>/and cannot be canonicalized as registry packages or resolved fromds_modules/. Name validation sharesis_valid_package_name.Entry precedence is package.json
module, thenmain, thenindex.mjswhen neither field exists or the manifest is absent. Malformed manifests, invalid explicit entries, missing files, and entry paths escaping the package fail without silently falling back.The project gate requires the exact
@js/<name>declaration in dependencies/devDependencies, a matching deka.lock package tuple using the existing pm format, and a resolvable vendored entry. External stdlib roots, waived stdlib lockfiles, aliases, and local links do not waive these requirements. Integrity verification remains with pm.Validation:
cargo test --locked(43 passed, including 10 new integration tests),cargo clippy --locked --all-targets -- -D warnings,cargo fmt --all -- --check, andgit diff --check.No version bump or tag; Ava owns the 0.2.0 release. Existing public-ci/release environment configuration is unchanged.
Refs dekaruntime/rfd#39 and dekaruntime/deka#881.
-codex