refactor: switch minimatch to micromatch

[curbengh]

What does it do?

micromatch is a replacement of minimatch. It supports multiple patterns in an array, without string-to-array conversion, along with other globbing features. It's also faster and updated much more frequently (micromatch vs minimatch). It's already utilized in hexo, indirectly through chokidar dep. npm ls --depth 5 shows 4 instances of it.

Using micromatch@4 is rather drastic since it depends on Node >=8, considering other deps currently use micromatch@3. But it's not a major issue, as Node 6 will be eventually dropped (#3508).

Personally, I would prefer to enable the matchBase option. With this option, I can just use 'ignore-this.txt' to exclude that file (assuming the filename is unique. I'm aware of the underscore ignore), instead of '**/ignore-this.txt'. When globbing is used, if I want to exclude all .txt, I only need '*.txt', instead of '**/*.txt'. In the case of #3306, it can be just 'abc*'. The doc needs to be updated though if this behavior is introduced.

How to test

git clone -b micromatch https://github.com/weyusi/hexo.git
cd hexo
npm install
npm test

github page: https://github.com/weyusi/hexo-testing

Pull request tasks

• Add test cases for the changes.
• Passed the CI test.
  • will not pass in Node 6 environment.

[coveralls]

Coverage decreased (-0.002%) to 97.146% when pulling 8d83bdf on weyusi:micromatch into c2e4672 on hexojs:master.

[yoshinorin]

@weyusi
Thank you very much :)
As you know we haven't decided to drop Node.js v6... Please wait for a while.

[tcrowe]

I like the idea and your arguments are valid, @weyusi. Thank you for the idea and PR.

[curbengh]

is matchBase option okay?

Edit: I just tested matchBase option. While it's useful to ignore a filename in any folder, it doesn't work if a folder needs to be specified (e.g. **/foo/bar.txt or **/*/foo/bar.txt).

[curbengh]

I've rebased. Ready to be reviewed.

[tcrowe]

I tested it and it worked 👍🏻

Thank you @weyusi