lint-staged
Nest
Our great sponsors
lint-staged | Nest | |
---|---|---|
50 | 311 | |
12,773 | 63,607 | |
1.5% | 1.7% | |
8.4 | 9.9 | |
3 days ago | 3 days ago | |
JavaScript | TypeScript | |
MIT License | 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.
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.
-
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.
-
Just deployed my first web app. I know it's simple, but any feedback would be greatly appreciated..
I'm noticing a lack of formatting in your JS. Some files have semi-colons, some don't. Some lines are indented more than others. There's inconsistent use of single vs double quotes. You can easily standardize formatting with a Prettier. It's recommend to run it with husky and lint-staged on every commit so you never commit code which is unformatted. (Same with your HTML and CSS which are inconsistently formatted making it harder to read.)
Nest
-
Containerize your multi-services app with docker compose
Back: a graphQL server built with Nestjs
-
Full Stack Web Development Concept map
NestJS - opinionated more scalable, but harder to learn docs
-
Don't go all-in Clean Architecture: An alternative for NestJS applications
Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):
- Utilizando Testcontainers para Testes de Integração com NestJS e Prisma ORM
-
A Gentle Introduction to Containerization and Docker
It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.
-
Scalable REST APIs with NestJS: A Testing-Driven Approach
describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });
-
Rust GraphQL APIs for NodeJS Developers: Introduction
In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:
-
A Step-by-Step Guide to Implement JWT Authentication in NestJS using Passport
The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.
-
From Frontend to Backend
That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/
-
Best NodeJS frameworks for seamless backend development
Community stats: NestJS has a large community with 60.5k stars and 7.2k forks on GitHub. 12,033 are tagged 'nestjs' on StackOverflow and an active discord community of 43,436 is also there to support fellow developers.
What are some alternatives?
SailsJS - Realtime MVC Framework for Node.js
Koa - Expressive middleware for node.js using ES2017 async functions
loopback-next - LoopBack makes it easy to build modern API applications that require complex integrations.
feathers - The API and real-time application framework
Ts.ED - :triangular_ruler: Ts.ED is a Node.js and TypeScript framework on top of Express to write your application with TypeScript (or ES6). It provides a lot of decorators and guideline to make your code more readable and less error-prone. ⭐️ Star to support our work!
Moleculer - :rocket: Progressive microservices framework for Node.js
Django - The Web framework for perfectionists with deadlines.
tsoa - Build OpenAPI-compliant REST APIs using TypeScript and Node
Hapi - The Simple, Secure Framework Developers Trust
Meteor JS - Meteor, the JavaScript App Platform
InversifyJS - A powerful and lightweight inversion of control container for JavaScript & Node.js apps powered by TypeScript.
trpc - 🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.