prettier-plugin-rust
typescript-eslint
| prettier-plugin-rust | typescript-eslint | |
|---|---|---|
| 10 | 123 | |
| 167 | 14,612 | |
| - | 0.9% | |
| 4.1 | 9.9 | |
| 12 months ago | 5 days ago | |
| Rust | TypeScript | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
prettier-plugin-rust
- Oxlint – written in Rust – 50-100 Times Faster than ESLint
-
Is rustfmt abandoned? Will it ever format `let ... else` syntax?
Same code formatted by Prettier Rust
-
Minimalist Rust formatter as an alternative to rustfmt?
There are alternatives to rustfmt: Prettier Rust and genemichaels
- Prettier Rust: An opinionated code formatter that autocorrects bad syntax
-
Configuring rust format to add line break before comments start
If you're open to using an alternative, here's how Prettier Rust would format your snippet:
- Prettier code formatter for Rust
- Prettier for Rust
typescript-eslint
-
Mastering Type-Safe JSON Serialization in TypeScript
Typescript-eslint can assist in this task. This tool helps identify all instances of unsafe any usage. Specifically, all usages of JSON.parse can be found and it can be ensured that the received data's format is checked. More about getting rid of the any type in a codebase can be read in the article Making TypeScript Truly "Strongly Typed".
-
Oxlint – written in Rust – 50-100 Times Faster than ESLint
> Only lint files that have changed? How hard that is?
Quite hard, especially since type-aware rules from e.g. https://typescript-eslint.io/ mean that changing the type of a variable in file A can break your code in file B, even if file B hasn't changed.
-
How to Do a TypeScript Conversion: an opinionated take on gradual conversions
The article only touches this: when converting to TypeScript, `any` is useful, but in the end you don't want this type in your codebase - so don't forget to use typescript-eslint [0] and turn on those no-unsafe-* rules which guard against `any` leaking into your code.
[0] https://github.com/typescript-eslint/typescript-eslint
- How do I add additional rules to my typescript-eslint settings?
- What's the best config for typescript-eslint?
- How do you add angular-eslint to your typescript-eslint config?
- What's the best typescript-eslint config?
-
The Best ESLint Rules for React Projects
By convention, React components should be named in PascalCase. @typescript-eslint has the config we need, and though we can't specifically target React components, we can target variables (and set some other conventions while we're at it):
- Open source public fund experiment - One and a half years update
- Never touch those //ts-ignores
What are some alternatives?
rustfmt - Format Rust code [Moved to: https://github.com/rust-lang/rustfmt]
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
rustfmt - Format Rust code
angular-eslint - :sparkles: Monorepo for all the tooling related to using ESLint with Angular
topiary
ts-standard - Typescript style guide, linter, and formatter using StandardJS
darker - Apply black reformatting to Python files only in regions changed since a given commit. For a practical usage example, see the blog post at https://dev.to/akaihola/improving-python-code-incrementally-3f7a
zod - TypeScript-first schema validation with static type inference
prettyplease - A minimal `syn` syntax tree pretty-printer
node-clinic - Clinic.js diagnoses your Node.js performance issues
cbfmt - A tool to format codeblocks inside markdown and org documents.
ts-node - TypeScript execution and REPL for node.js