Conversation
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.
Refs #698.
Clarify in the README and
oneChangePerTokenoption documentation thatdiffWords's default whitespace-insensitive mode retains overlapping whitespace between tokens. Include the reported example and point callers who need separate whitespace tokens todiffWordsWithSpace.This documents existing behavior; it leaves the runtime semantics unchanged.
Validation on Node 24.19.0: build, lint, type checks and ESM/CommonJS examples pass; 45 word-diff tests pass. With the project's Babel preload and an LF README, the full suite has 315 passes and the same three failures on base and patch: two Windows file-mode assertions and a hunk-test timeout. The initial
yarn testrun stopped loading the README example from a CRLF checkout.