eslint-plugin-import-x
eslint-plugin-import-x copied to clipboard
un-ts
A fork of `eslint-plugin-import` using `get-tsconfig` to replace `tsconfig-paths` and heavy `typescript` under the hood.
The [documentation URL generator](https://github.com/un-ts/eslint-plugin-import-x/blob/master/src/utils/docs-url.ts) function appears to have been broken by forking and changing versions. ```ts import pkg from '../../package.json' const repoUrl = 'https://github.com/un-ts/eslint-plugin-import-x' export const docsUrl = (ruleName: string,...
The resolver currently supports three reference methods: - name -> eslint-import-resolver-name - npm package name - filesystem path I propose that it support the direct use of any object satisfied...
It appears that the source code requires `tslib`: `node_modules/eslint-plugin-import-x/lib/index.js` ```js "use strict"; const tslib_1 = require("tslib"); const electron_1 = tslib_1.__importDefault(require("./config/electron")); const errors_1 = tslib_1.__importDefault(require("./config/errors")); const react_1 = tslib_1.__importDefault(require("./config/react")); // …...
Currently, `eslint-plugin-import-x` patches `@typescript-eslint/utils` to add custom properties like the `category` and modify properties like the `recommended`. The PR accomplishes the same thing, by doing some TypeScript exercises instead.
I haven't remove the `resolver` concept in `eslint-plugin-import-x
Likely depends on https://github.com/import-js/eslint-plugin-import/issues/2556 but it's good to track nonetheless. Ref: https://github.com/eslint/eslint/issues/18093
Right now, `eslint-plugin-i` does not support `eslint-define-config` or `typescript types` at all. Does `eslint-plugin-i` want to support it natively? (This would require shipping `.d.ts` files), or should I add https://github.com/eslint-types/define-config-plugin-types/tree/main/types/i...
https://github.com/dominikg/tsconfck vs https://github.com/privatenumber/get-tsconfig cc @privatenumber --- related https://github.com/import-js/eslint-import-resolver-typescript/issues/262
tslib is required as a runtime dependency but not installed in this project. Fixes #73.
I would like to see written in readme, at the beginning, in easy language for people that do not understand technical terms, what are the differences we should expect between...
