Releases: manidlou/node-klaw-sync
Releases · manidlou/node-klaw-sync
v7.0.0
19 Mar 18:59
Compare
Sorry, something went wrong.
No results found
7.0.0 / 2025-03-17
Changed
Use lstatSync instead of statSync. [#20 ] (Thanks to @vic3king )
v6.0.0
24 Jun 01:33
Compare
Sorry, something went wrong.
No results found
6.0.0 / 2018-09-22
Added
traverseAll option. It would allow to traverse all subdirectories regardless of filter option. [#13 ] (Thanks to @jskrzypek )
v5.0.0
06 Sep 06:37
Compare
Sorry, something went wrong.
No results found
5.0.0 / 2018-09-05
Changed
Updated the algorithm to handle depthLimit option properly. #12 (Thanks to @Geelik )
v4.0.0
30 Apr 07:39
Compare
Sorry, something went wrong.
No results found
4.0.0 / 2018-04-30
Removed
BREAKING Removed noRecurseOnFailedFilter option because it was counter-intuitive and confusing.
Added
fs option. It is useful when mocking fs object.
depthLimit option. It can be used to specify the number of times to recurse before stoppig.
v3.0.2
22 Oct 05:58
Compare
Sorry, something went wrong.
No results found
3.0.2 / 2017-10-21
Use var instead of let in for loop.
v3.0.0
06 Aug 21:26
Compare
Sorry, something went wrong.
No results found
3.0.0 / 2017-08-06
Changed
graceful-fs is now a regular dependency, and is always loaded. This should speed up require time.
v2.1.0
26 Apr 03:34
Compare
Sorry, something went wrong.
No results found
2.1.0 / 2017-04-25
Fixed
Apply opts.nodir and opts.nofile when filter option is used.
v2.0.0
24 Apr 02:37
Compare
Sorry, something went wrong.
No results found
2.0.0 / 2017-04-23
Removed
BREAKING: Removed support for ignore option. Instead, filter option can be used. See: [#1 ]
Added
filter option. A function that gets one argument fn({path: '', stats: {}}) and returns true to include or false to exclude the item.
noRecurseOnFailedFilter option to prevent unnecessary traversal of unwanted directories when filter function is used.
v1.1.2
17 Feb 23:18
Compare
Sorry, something went wrong.
No results found
1.1.2 / 2017-02-17
Changed to traditional for loop instead of using Array.forEach() because of better performance.
v1.1.1
05 Feb 09:06
Compare
Sorry, something went wrong.
No results found
1.1.1 / 2017-02-05
changed handling error to throw the exception