v3.0.4

Compare Source

v3.0.2

Compare Source

Changed

• Remove collision-test from pre-commit hook to unblock release process

Fixed

• Replace BigInt with bignumber.js for broader browser support (legacy browsers)
• Add export module field to package.json for better ESM compatibility

Added

• Implement CSPRNG using crypto.getRandomValues for enhanced security
• Add validation to throw error when length > 32

Documentation

• Fix typo: Change "Pseudo" to "Pseudo" in README.md
• Update link for PleaseRobMe.com

v3.0.1

Compare Source

v3.0.0

Compare Source

v8.0.2

Compare Source

• #​616Restored compatibility ofdiffSentences with old Safari versions. This was broken in 8.0.0 by the introduction of a regex with alookbehind assertion; these weren't supported in Safari prior to version 16.4.
• #​612Improved tree shakeability by marking the built CJS and ESM packages withsideEffects: false.

v8.0.1

Compare Source

• #​610Fixes types fordiffJson which were broken by 8.0.0. The new bundled types in 8.0.0 only alloweddiffJson to be passed string arguments, but it should've been possible to pass either strings or objects (and now is). Thanks to Josh Kelley for the fix.

v8.0.0

Compare Source

• #​580Multiple tweaks todiffSentences:
  • tokenization no longer takes quadratic time on pathological inputs (reported as a ReDOS vulnerability by Snyk); is now linear instead
  • the final sentence in the string is now handled the same by the tokenizer regardless of whether it has a trailing punctuation mark or not. (Previously, "foo. bar." tokenized to["foo.", " ", "bar."] but "foo. bar" tokenized to["foo.", " bar"] - i.e. whether the space between sentences was treated as a separate token depended upon whether the final sentence had trailing punctuation or not. This was arbitrary and surprising; it is no longer the case.)
  • in a string that starts with a sentence end, like "! hello.", the "!" is now treated as a separate sentence
  • the README now correctly documents the tokenization behaviour (it was wrong before)
• #​581 -fixed some regex operations used for tokenization indiffWords taking O(n^2) time in pathological cases
• #​595 -fixed a crash in patch creation functions when handling a single hunk consisting of a very large number (e.g. >130k) of lines. (This was caused by spreading indefinitely-large arrays to.push() using.apply or the spread operator and hitting the JS-implementation-specific limit on the maximum number of arguments to a function, as shown athttps://stackoverflow.com/a/56809779/1709587; thus the exact threshold to hit the error will depend on the environment in which you were running JsDiff.)
• #​596 -removed themerge function. Previously JsDiff included an undocumented function calledmerge that was meant to, in some sense, merge patches. It had at least a couple of serious bugs that could lead to it returning unambiguously wrong results, and it was difficult to simply "fix" because it wasunclear precisely what it was meant to do. For now, the fix is to remove it entirely.
• #​591 - JsDiff's source code has been rewritten in TypeScript. This change entails the following changes for end users:

  • thediff package on npm now includes its own TypeScript type definitions. Users who previously used the@types/diff npm package from DefinitelyTyped should remove that dependency when upgrading JsDiff to v8.

    Note that the transition from the DefinitelyTyped types to JsDiff's own type definitions includes multiple fixes and also removes many exported types previously used foroptions arguments to diffing and patch-generation functions. (There are now different exported options types for abortable calls - ones with atimeout ormaxEditLength that may give a result ofundefined - and non-abortable calls.) See the TypeScript section of the README for some usage tips.

  • TheDiff object is now a class. Custom extensions ofDiff, as described in the "Defining custom diffing behaviors" section of the README, can therefore now be done by writing aclass CustomDiff extends Diff and overriding methods, instead of the old way based on prototype inheritance. (Ithink code that did things the old way should still work, though!)

  • diff/lib/index.es6.js anddiff/lib/index.mjs no longer exist, and the ESM version of the library is no longer bundled into a single file.

  • TheignoreWhitespace option fordiffWords is no longer included in the type declarations. The effect of passingignoreWhitespace: true has always been to makediffWords just calldiffWordsWithSpace instead, which was confusing, because that behaviour doesn't seem properly described as "ignoring" whitespace at all. The property remains available to non-TypeScript applications for the sake of backwards compatibility, but TypeScript applications will now see a type error if they try to passignoreWhitespace: true todiffWords and should change their code to calldiffWordsWithSpace instead.

  • JsDiff no longer purports to support ES3 environments. (I'm pretty sure it never truly did, despite claiming to in its README, since even the 1.0.0 release usedArray.map which was added in ES5.)

• #​601 -diffJson'sstringifyReplacer option behaves more likeJSON.stringify'sreplacer argument now. In particular:
  • Each key/value pair now gets passed through the replacer once instead of twice
  • Thekey passed to the replacer when the top-level object is passed in asvalue is now"" (previously, wasundefined), and thekey passed with an array element is the array index as a string, like"0" or"1" (previously was whatever the key for the entire array was). Both the new behaviours match that ofJSON.stringify.
• #​602 -diffing functions now consistently returnundefined when called in async mode (i.e. with a callback). Previously, there was an odd quirk where they would returntrue if the strings being diffed were equal andundefined otherwise.

v7.0.0

Compare Source

Just a single (breaking) bugfix, undoing a behaviour change introduced accidentally in 6.0.0:

• #​554diffWords treats numbers and underscores as word characters again. This behaviour was broken in v6.0.0.

v7.0.1

Compare Source

• Fix suport for spaces and periods in replacement string0df0d46

v7.0.0

Compare Source

Breaking

• Require Node.js 20cc39041
• Fix Unicode normalizationea8b961
  • Previously, it used the incorrectNFD Unicode normalization. It now uses the correctNFC normalization. This could be a breaking change if you stored the filenames and then compare, as they won't match. You could run aNFC normalization on the stored once to fix that.

Improvements

• Use grapheme-safe truncation98169ce
• Fix trailing spaces and periods handling43eea4d

v6.0.0

Compare Source

Breaking

• Require Node.js 16b5297cc

Improvements

• Prevent stripping of outer replaced characters (#​38)7d4846f

v5.1.1

Compare Source

• Fix overstripping of replacement character (#​33)69989b8
• FixmaxLength option being broken on files with no extension (#​30)a2ee598
• Account for dotfiles (#​32)6badd76
• Account for extension length when truncating filename (#​31)a16c224

v5.1.0

Compare Source

• Unicode normalize the filename4a0d964

v5.0.2

Compare Source

• Fix filenames truncated bymaxLength not keeping their extension (#​27)8c52cb1

v5.0.1

Compare Source

• Fix missing export of theOptions typefbb7353

v5.0.0

Compare Source

Breaking

• Require Node.js 12.20 (#​25)c2000ac
• This package is now pure ESM. Pleaseread this.

v7.0.0

Compare Source

⚠️ BREAKING CHANGES

• align to npm 11 node engine range (#​147)

Bug Fixes

• 69e0cbb#​147 align to npm 11 node engine range (#​147) (@​owlstronaut)

Chores

• c6866b9#​146 bump@​npmcli/template-oss from 4.26.0 to 4.27.1 (#​146) (@​dependabot[bot],@​npm-cli-bot)