Repository navigation
Remove range_check dependency - #229
Merged
Merged
Conversation
Replace range_check with a custom CIDR check using neoip's toUInt8Array and byte-level prefix matching. This removes a dependency with a broken CJS build (ip6 is ESM-only) and adds IPv6 CIDR support.
Cover IPv4/IPv6 CIDR boundaries, /32 and /128 single address blocks, and IPv4 vs IPv6 mismatch cases.
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.
Summary
range_checkwith a custom CIDR check using neoip'stoUInt8Arrayand byte-level prefix matchingip6is ESM-only), which blocked upgrading to range_check v4 (Bump range_check from 2.0.4 to 4.1.0 #215)inCidrimplementation supports both IPv4 and IPv6 CIDR blocks@eslint/jsandglobalsas missing devDependencies for eslint 10Test plan