eslint-plugin-import
lint-staged
eslint-plugin-import | lint-staged | |
---|---|---|
45 | 50 | |
5,314 | 12,885 | |
0.7% | 0.9% | |
8.3 | 8.2 | |
2 days ago | 7 days ago | |
JavaScript | JavaScript | |
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.
eslint-plugin-import
-
Speeding up the JavaScript ecosystem – Polyfills gone rogue
[2]: https://github.com/import-js/eslint-plugin-import/pull/2447#...
-
The Best ESLint Rules for React Projects
Finally, I'd also suggest requiring named exports via import:
-
PURISTA - Thanks to amazing open-source software
eslint-plugin-import
-
How to prevent other devs from using components from UI library directly?
You can 1. use a rule like this one to ensure that no one imports from antd and 2. limit what they can import from your library via https://nodejs.org/api/packages.html#main-entry-point-export
-
Need someone to explain why this happen regarding exporting
I'd check the eslint docs. They usually have a little write up about the rule.
-
React Component file naming convention?
Next, you add the ESLint rule or TypeScript configuration so it never happens again.
-
When to Create Standalone Components in Angular?
Are you using Eslint? It is possible to remove all the unused import on file level, but I don't remember if the setting is in the recommend config or the import/ordef plugin. If configured correctly, VS Code will prompt you with an option (CTRL+.) to "Delete all unused imports". It's only on file level though.
- People’s thoughts on ordering functions alphabetically in a react component?
-
3 popular Eslint rules that can make you write worse code.
Prefer default export (from airbnb style guide) I did drop default exports for a year now to use only named exports and they are actually (a slightly) better option. They provide a better DX, since you'll have autocomplete. The downside can be conflicts (which can be solved using an as to rename it). Don't refactor your entire codebase just to use it, but keep in mind for the next projects that named exports has better tradeoffs.
-
excluding folders/fildes when building
Yeah, the code under server should never get included unless you were to (transitively) import it from your entry point like App.tsx. Small suggestion, this is a good candidate for an ESLint rule if you use that.
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?
prettier-plugin-organize-imports - Make Prettier organize your imports using the TypeScript language service API.
commitlint - 📓 Lint commit messages
madge - Create graphs from your CommonJS, AMD or ES6 module dependencies
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript 🚀
eslint-plugin-svelte3 - An ESLint plugin for Svelte v3 components.
stylelint - A mighty CSS linter that helps you avoid errors and enforce conventions.
eslint-plugin-import-helpers - ESLint plugin to help enforce a configurable order for import statements
prettier - Prettier is an opinionated code formatter.
unimported - Find and fix dangling files and unused dependencies in your JavaScript projects.
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.
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]
volar - âš¡ Explore high-performance tooling for Vue [Moved to: https://github.com/vuejs/language-tools]