As a result there are new statistics (leftBrokenLinks, rightBrokenLinks, distinctBrokenLinks, totalBrokenLinks) and new entry type - broken-link. Broken links are no longer treated as errors.Tests are no longer part of published package.New field indicating reason for two entries being distinct.V2.4.0 New option to customize file/folder name comparison V3.0.0 Moved CLI component into separate project dir-compare-cli V3.1.0 Added ignoreAllWhiteSpaces and ignoreEmptyLines options Using this library to compare two files will ignore the name of the files.UI apps will be more responsive while comparison is ongoing Works 2x faster when comparing by content.Heap usage has decreased 3x compared to previous version.Async comparator improvements when comparing large directory structures.This behavior can be altered with Options.handlePermissionDenied. The comparison will be intrerrupted with an EACCES exception. Unreadable files or directories are normally reported as errors. Also statistics summarizes differences caused by symbolik links. If entries are different because of symlinks, reason will be different-symlink. These rules are applied in addition to the other comparison modes ie. both are symlinks but point to different locations.In this mode two entries with identical name are considered different if Using compareSymlink option causes dircompare to check symlink values for equality. Since 2.0 they are treated as a special type of entry - broken-link - and are available as stats ( totalBrokenLinks, distinctBrokenLinks.
Version 1.x treats broken links as ENOENT: no such file or directory. Unless compareSymlink option is used, symbolic links are resolved and any comparison is applied to the file/directory they point to.Ĭircular loops are handled by breaking the loop as soon as it is detected. The default builder can be used as an example. Const dircompare = require ( 'dir-compare' ) const options = const res = dircompare.
0 kommentar(er)
