v7.0.4

Compare Source

• PATCH Allows files named.{3,}, such as... for Linux / macOS (#​68)

ig.ignores('...')ig.ignores('....')// It will throw a RangeError in versions prior to 7.0.4, but it is ok if >= 7.0.4

An upgrade is recommended for all dependents

v7.0.3

Compare Source

v7.0.2

Compare Source

v7.0.1

Compare Source

v7.0.0

Compare Source

Minor feature

The primary feature introduced by7.0.0 is the.checkIgnore() method, which is most equivalent togit check-ignore -v. And also it allows to pass{pattern, mark?} as the parameter of.add() so that we could imitate the mechanism ofgit check-ignore as:

ig.add({pattern:'foo/*',mark:'60'})const{  ignored,  rule}=checkIgnore('foo/')if(ignored){console.log(`.gitignore:${result}:${rule.mark}:${rule.pattern} foo/`)}// .gitignore:60:foo/* foo/

Potential Incompatibilities

The only situation that7.0.0 might bring incompatibility is to.add() a< 7.0.0 instance into a>= 7.0.0 instance, which might occur when the current workspace has multiplenode-ignore versions installed, please be careful.

const{anotherIgnoreInstance}=require('./ignore-6.0-instance')// A 7.0.0 instanceignore().add(anotherIgnoreInstance)// It will break your code

Otherwise, in most cases, if you never do something above or there is only one version ofnode-ignore installed in the current workspace, it is quite safe to upgrade to7.0.0.

v6.0.2

Compare Source

v6.0.1: 6.x (== 5.3.2)

Compare Source

6.x

• The release of6.x is due to a mistake.
• Making an upgrade from5.x to 6.x for now actually changes nothing and does no harm, everyone could just upgrade or ignore the version.
  • Actually6.0.2 is5.3.2
• The next major release will be7.0.0

v6.0.0

Compare Source