{"repo":"denoland/deno_lint","free":true,"listed":false,"github":"https://github.com/denoland/deno_lint","clone":"git clone https://github.com/denoland/deno_lint.git","description":"Blazing fast linter for JavaScript and TypeScript written in Rust","language":"Rust","stars":1585,"topics":["deno","typescript","javascript","linters"],"license":"MIT","category":"dev-tools","readme_excerpt":"deno lint A Rust crate for writing JavaScript and TypeScript linters. This crate powers deno lint , but is not Deno specific and can be used as a standalone crate. It ships with a set of built-in rules, including a recommended set that is enabled by default and requires no configuration. Supported rules The list of available rules and their documentation is hosted at docs.deno.com/lint/rules. Example To see how deno lint is used as a crate, look at how it is integrated in deno . Developing Make sure to have the latest stable version of Rust installed, see rust-toolchain.toml. Contributing - If you are going to work on an issue, mention so in the issue comments before you start working on the issue. - Please be professional in the forums. We follow Rust's code of conduct (CoC). - Ask for help in the community chat room. Submitting a Pull Request Before submitting, please make sure the following is done: 1. That there is a related issue and it is referenced in the PR text. 2. There are tests that cover the changes. 3. Ensure cargo test passes. 4. Format your code with deno run --allow-run tools/format.ts . 5. Make sure deno run --allow-run --allow-env tools/lint.ts passes. 6. If you've added a new rule, open a PR to denoland/docs with documentation for the rule.","default_branch":null,"files":null,"tree":[],"storefront":"/r/denoland","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/denoland/deno_lint/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}