merger-js - npm Package Versions

v2.2.0 - 17/04/2018

• Made native OS notifications optional and configurable through the CLI;
• Improvement and minor fixes/refactorings on the import parser;
• Other minor improvements/refactorings/bug fixes.

v2.1.0 - 10/04/2018

• Added the "set" command, to edit the merger configuration file through the CLI (README.md for more info);
• Minor refactorings and bug fixes.

v2.0.8 (Patch) - 09/04/2018

• Added .git to .npmignore. The .git folder was beeing installed along with merger-js, which caused errors during updates. The command "merger update", and normal updates by "npm i merger-js -g", are now functional.<br/> It is advised to reinstall merger-js:<br/>

1. "npm rm merger-js -g"<br/>
2. "npm i merger-js -g"

v2.0.5/6/7 (Hotfixes) - 09/04/2018

• Sent the wrong files to npm multiple times and had one error in package.json.<br/> No changes.

v2.0.4 - 09/04/2018

• Added data from last version (2.0.3) to GitHub (not pushed to GitHub);
• Removed ability to set OS native notifications off. It introduced a bug. Removed the feature until further development;
• Made updates optional;
• Added the command "merger update".

v2.0.3 - 07/04/2018

• BUG: Solved a bug where the inputs were only beeing parsed on the first build instead of on each build. If a user reorganized their imports, it wouldn't affect the build. Bug solved.
• Added an HTTP request to the npm-registry when the user runs merger, in order to check if there's a new version available;
• Made OS native notifications optional.

v2.0.2 - 05/04/2018

• Quick fix to a bug inserted on the last patch;
• Solved minor package security vulnerabilities (snyk).

v2.0.1 - 05/04/2018

• The imports on the source file are now parsed at build time. This enables adding/removing/reorganizing build files by simply just adding/removing/reorganizing @import comments;
• Improved the imports parser;
• Tested imports from diferent directories;
• Minor code fixes and refactorings.