findings: JSR npm-compat consumption (layout split, deno package.json interactions) - #100
Merged
Conversation
… interactions) Findings 26-29 from the consumer migration off the npm-git facade (webcrypto#385, tls#46, websocket#55, webrtc-datachannels#162): the npm-compat tarball and deno's native materialization lay the same package out differently; deno 2.9 rejects scoped npm aliases in package.json; deno install's two scopes prune each other's node_modules (bare install + deno check is the stable sequence); and minimumDependencyAge exclusions must cover the npm-form name for npm-compat consumption.
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
2 participants
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.
Appends findings 26–29 from the consumer migration (webcrypto#385, tls#46, websocket#55, webrtc-datachannels#162): the two-layout split between npm-compat tarballs and deno-native materialization (the root cause behind #97), deno 2.9's scoped-npm-alias parse failure,
deno installscope pruning and the bare-install +deno checksequence, andminimumDependencyAge's npm-form naming. Docs-only.