fast-glob dependency update

What's new ?

• fix(deps): update dependency fast-glob to v3.2.5 d59c0e2
• docs: add installation section (closes #69) d93ebf0

Internals

• chore(deps): update dependency husky to v4.3.8 541823a
• chore(deps): update dependency husky to v4.3.7 e1b0789
• chore(deps): bump node-notifier from 8.0.0 to 8.0.1 (#66) 2c0aba8
• chore(deps): update actions/setup-node action to v2 (#65) 65f9d2d
• chore(deps): update dependency husky to v4.3.6 (#64) c3fdf90

v2.0.0...v2.0.1

Changed parser to xmlbuilder2

What's new ?

Internals

XML parser/serializer library changed from xmldom to xmlbuilder2.

• xmldom was source of issue #59, and has no options for fixing that issue.
• xmlbuilder2 is faster than xmldom, is maintained better and is successor of extremely popular xmlbuilder package. Also, it is more standard compliant

Breaking changes

There are no breaking changes in both package api and cli, however:

• xml parser switch may affect contents of combined xml
• xmlbuilder2 does not support xml version 1.1, so junit-report-merger won't be able to process xml files with version 1.1 anymore. To my knowledge no tools use xml version 1.1 in their test reports, so this should not affect people.

Added cli (called jrm) and glob support

What's new ?

Features

1. Added CLI (called jrm). See CLI section for more info.
2. All api methods now support both callback-style and promise-based style.
   Love async/await? You will be fine! Forced to pass Node callbacks around? No problem, all api methods accept callbacks as well.
3. Added glob support for mergeFiles api method.
   Glob matching is powered by fast-glob.
   See mergeFiles for more info and usage examples.
4. Updated supported Node.js versions to 10, 12 and 14.
   Package may work on other versions, but we run tests only for Node 10, 12 and 14. For other versions you are on your own.

Internals

1. Switched to Jest
2. Increased test coverage
3. Switched to GitHub actions
4. Rewrote whole code in modern JavaScript
5. Added Prettier

Breaking changes

There are no breaking changes, however the whole code has been rewritten in modern JavaScript.
As a result we dropped support for Node 6 and 8.