You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Webpack config file is written in TS and type-checked on test/release.
With v4 of fork-ts-checker-webpack-plugintsc started to complain about a not found declaration file for eslint
node_modules/fork-ts-checker-webpack-plugin/lib/issue/eslint/EsLintIssueFactory.d.ts:1:25 - error TS7016: Could not find a declaration file for module 'eslint'. '/MY_PROJECT_DIR/node_modules/eslint/lib/api.js' implicitly has an 'any' type.
Try `npm install @types/eslint` if it exists or add a new declaration (.d.ts) file containing `declare module 'eslint';`
1 import * as eslint from 'eslint';
~~~~~~~~
node_modules/fork-ts-checker-webpack-plugin/lib/issue/eslint/FileAwareEsLintMessage.d.ts:1:25 - error TS7016: Could not find a declaration file for module 'eslint'. '/MY_PROJECT_DIR/node_modules/eslint/lib/api.js' implicitly has an 'any' type.
Try `npm install @types/eslint` if it exists or add a new declaration (.d.ts) file containing `declare module 'eslint';`
1 import * as eslint from 'eslint';
Thanks for the report. @piotr-oles how do you want to proceed with this? I'd suggest we don't want to make @types/eslint a dependency.
I suspect this is a side effect of moving to use import * as eslint from 'eslint'; style imports rather than targeted ones that only import the types being used.
If so, this could probably be fixed by switching back to the import { TYPE } from 'eslint'; style imports
Current behavior
My Webpack config file is written in TS and type-checked on test/release.
With v4 of
fork-ts-checker-webpack-plugin
tsc started to complain about a not found declaration file foreslint
Expected behavior
type-checking should pass
Steps to reproduce the issue
tsconfig.json
webpack.config.ts
and then run
Environment
tslintThe text was updated successfully, but these errors were encountered: