Repository navigation
fix(updater): range block uses the global URL for a path feed root - #92
Merged
Merged
Conversation
Shared range-52w block re-applied: pathToFileURL is wrapped in the global URL, so the IDE type check passes with an older nested @types/node too (found in Amplify).
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.
What
Re-applies the shared
range-52wblock (workspace etf-std): one line,pathToFileURL(...)wrapped innew URL(... .href).Why
With an older nested
@types/nodethe node URL type is not the globalURL(TS2345, found in Amplify); the block stays byte-identical in every brand.Checks
bun testTC_MODE=esnext tc/check.sh .clean