Linux arguments support

Breaking Changes:

• NONE! Your code should work exactly the same without changing anything.

Enhancements:

• You can now pass in arguments with your Linux shortcut, just like you can with Windows (to my knowledge this is not possible with OSX)

Special thanks to @unmellow for bringing this to my attention (#30).

Maintenance:

• Updated dependencies
• Updated documentation

Code Quality:

• Linting and Test coverage remains at 100%
• E2E tests all passing

Code Changes

• v1.3.0...v1.4.0
• v1.2.1...v1.4.0
• v1.2.0...v1.4.0
• v1.1.0...v1.4.0
• v1.0.2...v1.4.0
• v1.0.1...v1.4.0
• v1.0.0...v1.4.0

Support for older versions of Node

Breaking Changes:

• NONE! Your code should work exactly the same without changing anything.

Enhancements:

• Runs in Node 4.0.0+
• Tested on Windows XP
• Better documented Node and OS support
• Improved linting enforcement for JSDocs
• All methods and functions are documented now via JSDoc blocks

Special thanks to @shun634501730 for bringing this to my attention (#26).

Maintenance:

• Updated dependencies
• Updated documentation

Code Quality:

• Linting and Test coverage remains at 100%
• E2E tests all passing

Code Changes

• v1.2.1...v1.3.0
• v1.2.0...v1.3.0
• v1.1.0...v1.3.0
• v1.0.2...v1.3.0
• v1.0.1...v1.3.0
• v1.0.0...v1.3.0

Start menu shortcuts

Breaking Changes:

• NONE! Your code should work exactly the same without changing anything.

Enhancements:

• Documented how to add a shortcut to the start menu in Windows and Linux (in README.md)

Special thanks to @fp07 for bringing this to my attention (#24).

Maintenance:

• Updated dependencies
• Updated documentation
• Improved E2E testing locally
• Added stricter linting rules for JSDocs and improved existing JSDoc blocks

Code Quality:

• Linting and Test coverage remains at 100%
• E2E tests all passing

Code Changes

• v1.2.0...v1.2.1
• v1.1.0...v1.2.1
• v1.0.2...v1.2.1
• v1.0.1...v1.2.1
• v1.0.0...v1.2.1

Add "workingDirectory" feature to Windows shortcuts

Breaking Changes:

• NONE! Your code should work exactly the same without changing anything.

Enhancements:

• Added a new API option for Windows called workingDirectory. It lets you set the "current working directory" for the shortcut application when launched. This feature should have been included in the library earlier but was overlooked.

Special thanks to @Tixxxon for bringing this to my attention (#21).

Maintenance:

• Updated dependencies
• Updated documentation

Code Quality:

• Linting and Test coverage remains at 100%
• E2E tests all passing

Code Changes

• v1.1.0...v1.2.0
• v1.0.2...v1.2.0
• v1.0.1...v1.2.0
• v1.0.0...v1.2.0

Major rewrite, 100% test coverage

Breaking Changes:

• NONE! Your code should work exactly the same without changing anything.

Enhancements:

• Improve Linux "type" defaulting
  • Defaults to "Link" if filePath starts with 'https://' or 'http://'
  • Defaults to "Directory" if filePath exists and is a folder
  • Defaults to "Application" otherwise
• Set up Jest for unit tess.
• Achieve 100% test coverage
• End-to-End (E2E) test coverage set up to automate testing the creation of an actual shortcut on each OS.
• Log error if the windows.vbs file cannot be found for some reason, rather than popping up a WSCRIPT alert dialogue box
• Added "No Ideologies" Code of Conduct
• Resolve all open issues
• Improve logic for validating passed in options before execution in many locations.

Maintenance:

• 3,727 lines of code changed since last version
• update dependencies
• Switch from Travis-CI to GitHub Actions
• Enforce CI passing and up-to-date branches before merging to master
  • Linting
  • Unit Tests
  • End-to-End testing
  • On Latest Windows, OSX, and Ubuntu
• Improved the .editorconfig settings
• Updated README.md

Code Quality:

• Split out code into files, rather than just using one really long file
• Improve some code documentation (more descriptive variable names, links to online docs)
• Improve linting

Code Changes

• v1.0.2...v1.1.0
• v1.0.1...v1.1.0
• v1.0.0...v1.1.0

Bugfix

• Fixed a bug where you would get a console error if you didn't pass in a customLogger

Update documentaiton

• Cleaned up the docs to be more accurate and fix some typos

Initial release

• Supports Windows, Linux, OSX
• Has comprehensive validation
• Human readable error messages
• Synchronous only
• Works in Node.js and NW.js
• Fully documented