Test: Added StandardJS (Static Analysis)

[aliciach1]

What problems does this tool catch?
This tool catches style issues, such as inconsistent indentation, as well as simple syntactical issues, such as using == or ===, or detecting unused variables.

What types of customization are possible or necessary?
We can define our own globals and environments. However, we cannot change the syntax rules.

How can/should this tool be integrated into a development process?
This tool should be used throughout integration, and should be used to fix syntax issues in code as it is committed to the repository.

Are there many false positives? False negatives? True positive reports about things you don’t care about?
There are false positives for when our globals are not added, for example when we call "it" in our testing suite. There are also true positives for when the indents are made of tabs and not spaces, which directly contradicts the syntax rules for eslint and is unhelpful.

Strengths: easy to implement, does not require extensive dependencies.

Weaknesses: The formatting conventions the standard tests against conflicts with those of eslint. For example, eslint expects indents to be made up of tabs, while standard expects them to be made up of spaces. Thus, it is illogical to put both in the testing suite.

Changes made: ran standard --fix, then npm run lint -- --fix. also added standard to the tests in package.json.

Attached is an excerpt and a screenshot of the terminal output when running standard.
standard_terminal_output.txt