Repository navigation
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| } | ||
| rewritten := make([]byte, 0, len(dist)-len(urlMember.value(dist))+len(encoded)) | ||
| rewritten = append(rewritten, dist[:urlMember.valStart]...) | ||
| rewritten := make([]byte, 0, len(dist)-len(urlMember.Value(dist))+len(encoded)) |
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.
npm metadata rewriting currently depends on
handler.Proxy, which pulls SQL drivers, cloud SDKs and metrics into its import graph. Move the transformation intointernal/metadata/npmwith explicit policy, evaluation time, public URL and hosted-version inputs. The existing npm routes use the extracted code, and npm and Composer share the JSON scanner throughinternal/jsonscan.This implements the npm portion of the first experiment in #501. Fetching, storage, caching and HTTP responses stay in the native handler, with optional callbacks preserving per-version logging. The extracted code can run under Go and TinyGo/WASI without new dependencies or compiler-specific branches. Cooldown uses one evaluation time per rewrite; the HTTP response formats and policy rules are preserved.