The following tools provide various options to report on code based on slightly different philosophies. They can be run as part of an automated build step, as an editor plugin, or both.
- TSLint for TypeScript.
- JSHint was a common choice prior to ESLint.
Shared editor configuration
Tabs or spaces? Any time a group of developers starts a conversation about file formatting standards, there’s bound to be disagreement.
A little tool called EditorConfig can be committed to the root of a project and used to share a few key stylistic choices around indentation, line ending, and character encoding. Plugins for a variety of IDEs and text editors will automatically pick up and enforce these configurations within the scope of the project.
How to write a simple, generic Result type to hold a value or Error.
How to integrate build-time or server-side syntax highlighting for markdown code fences with two libraries: markdown-it and Highlights (Atom’s syntax highlighting engine).