Google TypeScript Style
gts is Google's TypeScript style guide, and the configuration for our formatter, linter, and automatic code fixer. No lint rules to edit, no configuration to update, no more bike shedding over syntax.
To borrow from standardjs:
- No configuration. The easiest way to enforce consistent style in your project. Just drop it in.
- Automatically format code. Just run
gts fixand say goodbye to messy or inconsistent code. - Catch style issues & programmer errors early. Save precious code review time by eliminating back-and-forth between reviewer & contributor.
- Opinionated, but not to a fault. We recommend you use the default configuration, but if you need to customize compiler or linter config, you can.
Under the covers, we use eslint to enforce the style guide and provide automated fixes, and prettier to re-format code.
The easiest way to get started is to run:
npx gts initWhen you run the npx gts init command, it's going to do a few things for you:
- Adds an opinionated
tsconfig.jsonfile to your project that uses the Google TypeScript Style. - Adds the necessary devDependencies to your
package.json. - Adds scripts to your
package.json:check: Lints and checks for formatting problems.fix: Automatically fixes formatting and linting problems (if possible).clean: Removes output files.compile: Compiles the source code using TypeScript compiler.pretest,posttestandprepare: convenience integrations.
- If a source folder is not already present it will add a default template project.
The commands above will all run in the scope of the current folder. Some commands can be run on individual files:
gts check index.ts
gts check one.ts two.ts three.ts
gts check *.tsShow your love for gts and include a badge!
[](https://github.com/google/gts)Made with ❤️ by the Google Node.js team.
NOTE: This is not an official Google product.