rushstack
lint-staged
rushstack | lint-staged | |
---|---|---|
11 | 50 | |
5,607 | 12,885 | |
0.8% | 0.9% | |
10.0 | 8.2 | |
1 day ago | 8 days ago | |
TypeScript | JavaScript | |
GNU General Public License v3.0 or later | MIT License |
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.
rushstack
-
How do you handle eslint/prettier configs across multiple repos?
If you're looking to recreate the ease of a monorepo with eslint/prettier, I've used the rushstack eslint patch to ship an eslint package which is almost fully self-contained, not just config, but dependencies as well: https://github.com/microsoft/rushstack/tree/main/eslint/eslint-patch
-
Handling TypeScript in a monorepo
I highly recommend rushstack. Itās a suite of tools for managing TypeScript monorepos. I use it at work and never want to go back to working without it.
-
Are there build systems for the JS/TS world?
https://rushjs.io/ and https://rushstack.io/
-
Lerna has gone. Which Monorepo is right for a Node.js BACKEND now?
Rush Stack. Itās an opinionated, batteries-included toolset for working with large monorepos. Itās highly extensible and pluggable, and has built-in support for a lot of common tasks. My team uses it at work to support a couple dozen projects and at this point I canāt imagine managing a monorepo without it. It has significant adoption within and support from Microsoft, and monthly public dev meetings with contributors from a number of other companies, so I really donāt think itās going to disappear any time soon. From what Iāve seen, itās a very healthy project thatās continuing to grow in support and adoption.
-
Micro-frontends building blocks: Monorepos
Tools like Lerna, Bazel, Nx, Rush, Turborepo, to name a few. Lerna is probably the grand daddy of all monorepo tools. CRA, Babel, Jest are a few projects that use it. Bazel has been refined and tested for years at Google to build heavy-duty, mission-critical infrastructure, services, and applications. Turborepo is the monorepo for Vercel, the leading platform for frontend frameworks. These tools can help keep your monorepo workspaces fast, understandable and manageable.
-
Typescript book with web and/or node.js fundamentals?
We donāt use backend node, I work in a big typescript monorepo and use Typescript to build plugins for compiling, packing, and testing, leveraging Rush and Heft on the client side (https://github.com/microsoft/rushstack) run via node
-
Rush and changelog generation - Part 2
I guess I'm not alone wishing that rush uses commit messages for change log generation. It's actually not so difficult (once it's done š).
-
"We made an open source app that tells you the time so we are the leaders in open source"
See: ONNX/ONNX Runtime, VSCode, Rush, & countless others
- Dev corrupts NPM libs 'colors' and 'faker' breaking thousands of apps
-
Tell HN: Microsoft forks MIT licensed repo, and changes the copyright to them
To late to edit or delete my comment above but just to set it straight I just learned that the whole lerna debacle linked above was a nothing-burger aka āfake newsā.
https://github.com/microsoft/rushstack/issues/673#issuecomme...
lint-staged
-
How Automation Saved Me from Oops Moments: Never Skip Tests in Production Again!
We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.
-
Pre-commit with husky & lint-staged
Now you can config it in your package.json, here is the guide doc:
-
Automating code patterns with Husky
In the world of software development, maintaining consistent code quality and ensuring that the codebase adheres to predefined patterns and guidelines is crucial. However, manually enforcing these standards can be time-consuming and error-prone. This is where automation tools like Husky, Lint-Staged, Commitlint, and Commitizen come to the rescue. In this post, we will explore how these tools can be combined to streamline your development workflow.
-
500 lines in 2013 is 10k in 2023, inflation you know
This is wasted work that can and should be automated. Adding a linter and formatter on CI and a pre-commit hook such as lint-staged can do wonders.
-
Set up linting and formatting for code and (S)CSS files in a Next.js project
lint-staged is a package that can be used to run formatting and linting commands on staged files in a Git repo.
-
How do you handle eslint/prettier configs across multiple repos?
To answer your next question: I lint and format on save, and I use Git hooks installed by Husky and executed through Lint-Staged (this tool helps ensure your Git hooks only run on modified files, etc) to ensure there are no lint or formatting errors whenever making a commit or pushing code. This is helpful for teams, as some developers tend to forget to run lint tasks, or don't have the Prettier extension installed in their IDE. If there are lint errors, the commit is rejected until fixed. YMMV - you'll need to fine-tune the strictness of this based on the team's needs.
-
How to create and publish a TypeScript library with ease
Uses Husky Git hooks and Lint-staged pre-commit hooks.
-
How to Contribute on the First Day of a FrontendĀ Project
Something else to consider is applying linting and formatting before every git commit. A package like Lint-staged only lints and formats on staged items, ensuring all pushed code follows the standards in the repo. This allows developers to have their own formatting preferences when developing, while the code homogenizes on push. Linting pre-commit also avoids strict rules like no-console or no-unused-vars restricting a developer when writing code, when it should only apply in production. Imagine not being able to console log anything during development!
-
Commit Like a PRO
Lint-Staged Docs
-
How to beautify your code and make contributions easy?
Additionally, there are pre-commit hooks which can be setup to seamlessly validate and modify the source code before every commit. I followed Prettier documentation to create one. I ran npx mrm@2 lint-staged which installed husky and lint-stagedand added a configuration to the projectās package.json. Then, I modified the commands a little and that's it.
What are some alternatives?
turborepo - Incremental bundler and build system optimized for JavaScriptĀ and TypeScript, written in Rust ā including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
commitlint - š Lint commit messages
lerna - :dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript š
husky - Git hooks made easy š¶ woof!
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
angular-eslint - :sparkles: Monorepo for all the tooling related to using ESLint with Angular
prettier - Prettier is an opinionated code formatter.
typescript-monorepo-example - An example of setting up a Lerna monorepo with Visual Studio Code and TypeScript
graphql-code-generator - A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.
nodejs-api-starter - š„ Yarn v2 based monorepo template (seed project) pre-configured with GraphQL API, PostgreSQL, React, Relay, and Material UI. [Moved to: https://github.com/kriasoft/relay-starter-kit]
volar - ā” Explore high-performance tooling for Vue [Moved to: https://github.com/vuejs/language-tools]