eslint-config-xo-typescript
eslint-config-xo-typescript copied to clipboard
xojs
ESLint shareable config for TypeScript to be used with eslint-config-xo
Currently, the ESlint configuration will mark constant properties on classes as errors. For example: ``` class FNV { private static readonly PRIME = 16777619; private static readonly OFFSET = 2166136261;...
Hello, I think that the regex below can be improved to ignore all "exotic" keys: https://github.com/xojs/eslint-config-xo-typescript/blob/022fe2553537227c64c9856191fd45ebc7016d76/index.js#L19-L22 ```ts vite: { server: { proxy: { '/api': { target: 'http://localhost:3003', ws: true }...
[Repro.zip](https://github.com/xojs/eslint-config-xo-typescript/files/3908556/Repro.zip) ➡️ Run: ```sh npm i npm test ``` ❌ You get: ``` > xo a.ts:1:7 ✖ 1:7 a is assigned a value but never used. @typescript-eslint/no-unused-vars b.ts:undefined:undefined ✖ 0:0...
https://github.com/alexgorbatchev/eslint-import-resolver-typescript
Related to the rule [`@typescript-eslint/naming-convention`](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/naming-convention.md#allowed-selectors-modifiers-and-types). I regularly use global constants with UPPER_CASE style for constants that wont change in runtime. Not sure how to exactly specify that in the rules...
```js { "name": "my-awesome-project", "eslintConfig": { "extends": [ "xo", "xo-typescript" ] } } ``` I haven't tested fully, but it seems that this is not enough to enable the configuration...
By enabling XO prettier and using this plugin, you get duplicated errors with rules `@typescript-eslint/indent` and `@typescript-eslint/semi`. There should be auto compatibility as they are both integrated within `XO`.
Should this configuration enforce Microsoft's [`eslint-plugin-tsdoc` ](https://www.npmjs.com/package/eslint-plugin-tsdoc)plugin? > This ESLint plugin provides a rule for validating that TypeScript doc comments conform to the [TSDoc specification](https://github.com/microsoft/tsdoc).
The `@typescript-eslint/eslint-plugin` provides a [recommended config](https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/src/configs/eslint-recommended.ts) which turn off some Eslint rules that conflicts or doesn't work well with TypeScript. For example in a `types.d.ts` file with the following code:...
