Added StandardJS Static Test to Repository #51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
### What types of problems are you hoping your tooling will catch? What types of problems does this particular tool catch?
StandardJS is a static analysis tool that checks the code quality in JavaScript applications, making the code more readable and maintainable as it gets more complex and has more contributors. This tool is meant to catch issues in the code that make it less readable in hopes of fixing the syntax and enhancing readability and understandability.
### What types of customization are possible or necessary?
To customize, you can define global variables that could otherwise cause linter errors, ignore certain files or directories, specify the environment so the linter can adapt to it, customize the error output, and do many more things to customize it further. For this case, I chose to customize global variables and ignore directories like node_modules and tests to avoid linting these massive directories and speed up the process. Overall, these customizations are convenient but not necessary.
### How can/should this tool be integrated into a development process?
You should install the style linter with the command npm install standard --global. Then, you want to add the command "standard" to your testing commands in package.json so that you can run npm run static-test to return the result of StandardJS.
### Are there many false positives? False negatives? True positive reports about things you don’t care about?
There are few false positives or false negatives since this tool searches for and analyzes code quality. This means it's a simple process where the tool scans the code and identifies changes to enhance readability and quality.
### Screenshot of test running
