Access PATH variables directly for filePaths

TheJaredWilcurt released this 23 May 02:17

· 40 commits to main since this release

Breaking Changes:

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

Bug Fixes:

Previously if no value was set for a comment on Windows, it would default to the output file's name (without extension). This was not needed, as it is perfectly fine for this field to be an empty string. This has been corrected. Now if you do not set a comment on Windows, there won't be one.

Enhancements:

You can now set your filePath to be equal to an executable name directly if it is available in the user's PATH. For example, if you set it to 'node' or 'python' or 'cmd' and the user can access those from PATH variables, it will work automatically. You no longer need to hard code the full file path, which is useful since those paths may vary depending on system.

Special thanks to @andy-chili-wang for bringing this to my attention, and @sysrage for the advice on implementation (#39).

Maintenance:

Made many improvements to linting, including stricter JSDoc block enforcement and adopting a newer parser. Special thanks to the folks at eslint-plugin-jsdoc for their consistently fast improvements and issue resolutions:
Updated the .gitAttributes to use a more modern way of enforcing line endings with Git
Updated dependencies
Updated documentation
- Badges point to the renamed main branch
- Updated comment about dependencies
- Corrected a line on file extensions for Windows icons
- Fixes typos/improve clarity of meaning
- Document special path capabilites

Code Quality:

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

Code Changes

Assets 2