eslint-import-resolver-typescript
eslint-import-resolver-typescri
eslint-import-resolver-typescript | eslint-import-resolver-typescri | |
---|---|---|
2 | 1 | |
686 | - | |
1.3% | - | |
6.3 | - | |
7 days ago | - | |
TypeScript | ||
ISC 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-import-resolver-typescript
-
How to set up ESLint and Prettier in React TypeScript 5 project? 2023
eslint-import-resolver-typescript
-
Speeding up the JavaScript ecosystem part 2 – Module Resolution
Thanks, happy you enjoyed the article!
The PRs for the previous article were all merged. I originally wanted to do the same for this one, but I'm not sure if I have the time to fix all of them. Updating to a newer version of `resolve` already addresses the most notable issue with throwing more errors than necessary, but many parts of the ecosystem still use an old version.
Manged to land this PR in another package though https://github.com/import-js/eslint-import-resolver-typescri... . Performance there could be easily improved further there.
Another PR to an eslint plugin was unfortunately rejected as it broke node 4 support https://github.com/import-js/eslint-plugin-import/pull/2654 .
The other popular package that's used for module resolution is `enhanced-resolve` by the webpack folks and they expect the consumer to deal with passing the appropriate options. So there isn't really a single place to fix this.
eslint-import-resolver-typescri
-
Speeding up the JavaScript ecosystem part 2 – Module Resolution
Thanks, happy you enjoyed the article!
The PRs for the previous article were all merged. I originally wanted to do the same for this one, but I'm not sure if I have the time to fix all of them. Updating to a newer version of `resolve` already addresses the most notable issue with throwing more errors than necessary, but many parts of the ecosystem still use an old version.
Manged to land this PR in another package though https://github.com/import-js/eslint-import-resolver-typescri... . Performance there could be easily improved further there.
Another PR to an eslint plugin was unfortunately rejected as it broke node 4 support https://github.com/import-js/eslint-plugin-import/pull/2654 .
The other popular package that's used for module resolution is `enhanced-resolve` by the webpack folks and they expect the consumer to deal with passing the appropriate options. So there isn't really a single place to fix this.
What are some alternatives?
bun - Incredibly fast JavaScript runtime, bundler, test runner, and package manager – all in one
eslint-plugin-import - ESLint plugin with rules that help validate proper imports.
ESLint - Find and fix problems in your JavaScript code.
electron-react-boilerplate - A Foundation for Scalable Cross-Platform Apps
electron-react-boilerplate - A Foundation for Scalable Cross-Platform Apps [Moved to: https://github.com/electron-react-boilerplate/electron-react-boilerplate]