NattLua
typescript-eslint
Our great sponsors
| NattLua | typescript-eslint | |
|---|---|---|
| 1 | 123 | |
| 74 | 14,568 | |
| - | 1.5% | |
| 8.1 | 9.9 | |
| 25 days ago | 7 days ago | |
| Lua | TypeScript | |
| - | 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.
NattLua
-
Ezno
source and further explanation: https://github.com/capsAdmin/nattlua
Not sure if I have any big plans, I just think it's fun and interesting to work on and maybe I want to use it for my other Lua projects. I'm not very happy with the codebase as I've written it in Lua. I'm trying to bootstrap it but it's growing in complexity faster than I can bootstrap it. But one step at a time and I should be there someday, maybe I can even port it to some other language like Rust when I have a better understanding of what I'm actually doing. :)
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?
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
angular-eslint - :sparkles: Monorepo for all the tooling related to using ESLint with Angular
ts-standard - Typescript style guide, linter, and formatter using StandardJS
zod - TypeScript-first schema validation with static type inference
node-clinic - Clinic.js diagnoses your Node.js performance issues
ts-node - TypeScript execution and REPL for node.js
WSL - Issues found on WSL
eslint-plugin-import - ESLint plugin with rules that help validate proper imports. [Moved to: https://github.com/import-js/eslint-plugin-import]
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
eslint-plugin-jest - ESLint plugin for Jest
io-ts - Runtime type system for IO decoding/encoding
typescript-eslint-language-service - TypeScript language service plugin for ESLint