digraph-js
JavaScript library to make Directed Acyclic Graph construction and traversal easy, including deep circular dependency detection ♽ (by antoine-coulon)
eslint-plugin-import
ESLint plugin with rules that help validate proper imports. (by import-js)
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
| digraph-js | eslint-plugin-import | |
|---|---|---|
| 3 | 45 | |
| 36 | 5,320 | |
| - | 0.9% | |
| 4.9 | 8.3 | |
| 10 months ago | 9 days ago | |
| TypeScript | JavaScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
digraph-js
Posts with mentions or reviews of digraph-js.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-24.
-
Let's implement the Incremental/Affected pattern, the killer feature used by Turborepo, Nx, Rush and many more popular tools
Feel free to check the full example here used in the final part of the blog post.
-
Let's implement the Incremental/Affected pattern, the killer feature used by Turborepo, Nx and many more popular tools
Implementation of the Affected pattern using digraph-js
-
Master Directed Graphs by example with JavaScript
See an implementation of a circular dependency detection using the digraph-js library I wrote
eslint-plugin-import
Posts with mentions or reviews of eslint-plugin-import.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-09-21.
-
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.