Release It! π
typescript-eslint
Our great sponsors
Release It! π | typescript-eslint | |
---|---|---|
9 | 123 | |
7,529 | 14,568 | |
2.1% | 1.5% | |
8.3 | 9.9 | |
6 days ago | 5 days ago | |
JavaScript | 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.
Release It! π
-
Nx - Highlights of 2023
Open source libraries and frameworks share a common necessity: the need to develop multiple packages cohesively and efficiently while managing their versioning and publishing to NPM. Nx has emerged as a go-to choice for handling such open source monorepos (as we'll explore further in the next section of this blog post). Until recently, one area Nx did not address directly was versioning and release management. Traditionally, this gap has been filled with tools like release-it, changesets, or custom Node scripts, similar to our approach in the Nx repository.
- automatic changelog generation with CI
-
How does the typescript-eslint project generate its changelogs?
Hi. I'm maintaining a small monorepo and I'd like to learn techniques from large, mature projects like typescript-eslint. I assume they automate changelogs from commit logs and/or PRs, but I can't figure out how they do it by looking at their source code. I do know of tools like release-it that helps automate the process; do the typescript-eslint maintainers use such a tool, or use a homegrown one?
-
Quickly start developing your own npm package library with NestJS.
This is a quick start guide for setting up a NestJS project for creating your own package library with automated versioning and package publishing. https://github.com/Emgevorgyan/nestjs-package-quick-start
-
Package Publishing Reading & Resources
Release It! - This seems promising. A CLI tool that can be used in interactive or continuous integration mode. The big appeal for me is a Yarn workspaces specific plugin.
-
Monorepo is so frustrating...
Fine, but I need a package release tool and release-it tools looks good. I install, configure and on the last step - publishing - I find out that this lib does not support monorepo... https://github.com/release-it/release-it/issues/831 and the release-it-yarn-workspaces lib does not support the latest version of release-it https://github.com/rwjblue/release-it-yarn-workspaces/issues/68
-
My ideal Rust workflow
May be less relevant for your particular workflow (because npm-specific and because everything is internal for you), but Iβm a big fan of an alternative in the auto-release-generation space: the combo of release-it and release-it-lerna-changelog, which give you the same kind of automation but donβt require specific git commit messages, because instead the combo uses the GH API and labels to generate the changelog. This is a muuuuuch nicer experience for external contributors, because it puts the responsibility for that back on maintainers instead.
-
DynamoDB GUI with Electron, React & Typescript
Release It - To create tags, bump the versions, manage release betas and detect merged changes.
-
Writing a High Quality README! π₯
Release It
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?
semantic-release - :package::rocket: Fully automated version management and package publishing
eslint-config-google - ESLint shareable config for the Google JavaScript style guide
autochecker - β»οΈ Test your libraries in many different versions of NodeJS, Ruby, Java and many other languages
angular-eslint - :sparkles: Monorepo for all the tooling related to using ESLint with Angular
iProxy - π Cross platform Web debugging proxyοΌfork of LightProxyγLinux & ε€η½ε‘ζ―ζοΌ
ts-standard - Typescript style guide, linter, and formatter using StandardJS
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
zod - TypeScript-first schema validation with static type inference
prop-sets - Generate and test every possible instance of a component in React
node-clinic - Clinic.js diagnoses your Node.js performance issues
lightproxy - π Cross platform Web debugging proxy
ts-node - TypeScript execution and REPL for node.js