eslint-plugin-import
eslint-plugin-import-helpers
| eslint-plugin-import | eslint-plugin-import-helpers | |
|---|---|---|
| 45 | 1 | |
| 5,309 | 286 | |
| 0.7% | - | |
| 8.3 | 0.0 | |
| 9 days ago | over 1 year ago | |
| JavaScript | JavaScript | |
| 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.
eslint-plugin-import-helpers
-
Import hierarchy
Getting to know eslint-plugin-import-helpers
What are some alternatives?
prettier-plugin-organize-imports - Make Prettier organize your imports using the TypeScript language service API.
eslint-plugin-boundaries - Eslint plugin checking architecture boundaries between elements
madge - Create graphs from your CommonJS, AMD or ES6 module dependencies
eslint-plugin-unicorn - More than 100 powerful ESLint rules
eslint-plugin-svelte3 - An ESLint plugin for Svelte v3 components.
xo - ❤️ JavaScript linter with great defaults [Moved to: https://github.com/xojs/xo]
unimported - Find and fix dangling files and unused dependencies in your JavaScript projects.
XO - ❤️ JavaScript/TypeScript linter (ESLint wrapper) with great defaults
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]
eslint-plugin-snakecasejs - :pencil2: ESLint Plugin: enforce snake_case syntax on variables and function names
eslint-plugin-deprecated-props - ESLint plugin to report deprecated props usage
cjs-to-es6 - CLI to convert CommonJS to ES6 modules (UNMAINTAINED)