Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/google/gts
☂️ TypeScript style guide, formatter, and linter.
https://github.com/google/gts
formatter google linter typescript
Last synced: about 2 months ago
JSON representation
☂️ TypeScript style guide, formatter, and linter.
- Host: GitHub
- URL: https://github.com/google/gts
- Owner: google
- License: apache-2.0
- Created: 2017-07-31T20:32:29.000Z (about 7 years ago)
- Default Branch: main
- Last Pushed: 2024-07-28T10:10:59.000Z (about 2 months ago)
- Last Synced: 2024-07-29T04:57:09.531Z (about 2 months ago)
- Topics: formatter, google, linter, typescript
- Language: TypeScript
- Homepage: https://github.com/google/gts
- Size: 3.76 MB
- Stars: 5,023
- Watchers: 47
- Forks: 197
- Open Issues: 50
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- awesome-list - gts
README
# gts
> Google TypeScript Style
[![NPM Version][npm-image]][npm-url]
[![GitHub Actions][github-image]][github-url]
[![Known Vulnerabilities][snyk-image]][snyk-url]
[![codecov][codecov-image]][codecov-url]
[![TypeScript Style Guide][gts-image]][gts-url]
[gts][npm-url] 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][standardjs-url]:
- **No configuration**. The easiest way to enforce consistent style in your project. Just drop it in.
- **Automatically format code**. Just run `gts fix` and 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][eslint-url] to enforce the style guide and provide automated fixes, and [prettier][prettier-url] to re-format code.
## Getting Started
The easiest way to get started is to run:
```sh
npx gts init
```
## How it works
When you run the `npx gts init` command, it's going to do a few things for you:
- Adds an opinionated `tsconfig.json` file to your project that uses the Google TypeScript Style.
- Adds the necessary devDependencies to your `package.json`.
- Adds scripts to your `package.json`:
- `lint`: 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`, `posttest` and `prepare`: convenience integrations.
- If a source folder is not already present it will add a default template project.
### Individual files
The commands above will all run in the scope of the current folder. Some commands can be run on individual files:
```sh
gts lint index.ts
gts lint one.ts two.ts three.ts
gts lint *.ts
```
### Working with eslint
Under the covers, we use [eslint][eslint-url] to enforce the style guide and provide automated fixes, and [prettier][prettier-url] to re-format code. To use the shared `eslint` configuration, create an `.eslintrc` in your project directory, and extend the shared config:
```yml
---
extends:
- './node_modules/gts'
```
If you don't want to use the `gts` CLI, you can drop down to using the module as a basic `eslint` config, and just use the `eslint` cli:
```
$ eslint --fix
```
This opens the ability to use the vast `eslint` ecosystem including custom rules, and tools like the VSCode plugin for eslint:
- https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
## Badge
Show your love for `gts` and include a badge!
[](https://github.com/google/gts)
```md
[](https://github.com/google/gts)
```
## Supported Node.js Versions
Our client libraries follow the [Node.js release schedule](https://nodejs.org/en/about/releases/). Libraries are compatible with all current _active_ and _maintenance_ versions of Node.js.
## Can I use *gts* with the [pre-commit](https://pre-commit.com/) framework?
Yes! You can put the following in your `.pre-commit-config.yaml` file:
```yaml
repos:
- repo: https://github.com/google/gts
rev: '' # Use the sha / tag you want to point at
hooks:
- id: gts
```
## License
[Apache-2.0](LICENSE)
---
Made with ❤️ by the Google Node.js team.
> **_NOTE: This is not an official Google product._**
[github-image]: https://github.com/google/gts/workflows/ci/badge.svg
[github-url]: https://github.com/google/gts/actions
[prettier-url]: https://prettier.io/
[codecov-image]: https://codecov.io/gh/google/gts/branch/main/graph/badge.svg
[codecov-url]: https://codecov.io/gh/google/gts
[david-image]: https://david-dm.org/google/gts.svg
[david-url]: https://david-dm.org/google/gts
[gts-image]: https://img.shields.io/badge/code%20style-google-blueviolet.svg
[gts-url]: https://github.com/google/gts
[npm-image]: https://img.shields.io/npm/v/gts.svg
[npm-url]: https://npmjs.org/package/gts
[snyk-image]: https://snyk.io/test/github/google/gts/badge.svg
[snyk-url]: https://snyk.io/test/github/google/gts
[standardjs-url]: https://www.npmjs.com/package/standard
[eslint-url]: https://eslint.org/