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
It's very important to be aware that this plugin uses TypeScript's, not webpack's modules resolution. It means that you have to setup tsconfig.json correctly. For example if you set files: ['./src/index.ts'] in tsconfig.json, this plugin will check only index.ts for errors.
Does this mean that imports of index.ts will not be explored/checked? That was my initial interpretation, but then that behavior wouldn't match typescript's module resolution either - it would be basically no module resolution. I guess if build: true it would match, but if build: false then files array is just the entry points for the transpilation graph.
I'm trying to debug a build issue, and I need to gain confidence on this point, please. I'm running forked v6.2.1 and not getting any errors listed. Kind of like #319 except that's claimed to be fixed in v6.
The text was updated successfully, but these errors were encountered:
The plugin will use the same module resolution as TypeScript. The simplest option to check whether it's a configuration issue or a bug in the plugin is running the tsc command - in your case, it should be tsc --build --watch. If it works in TypeScript, then the issue is in the plugin, otherwise, the issue is in the configuration or TypeScript itself :)
-- https://github.com/TypeStrong/fork-ts-checker-webpack-plugin#modules-resolution
Does this mean that imports of index.ts will not be explored/checked? That was my initial interpretation, but then that behavior wouldn't match typescript's module resolution either - it would be basically no module resolution. I guess if
build: true
it would match, but ifbuild: false
thenfiles
array is just the entry points for the transpilation graph.I'm trying to debug a build issue, and I need to gain confidence on this point, please. I'm running forked v6.2.1 and not getting any errors listed. Kind of like #319 except that's claimed to be fixed in v6.
The text was updated successfully, but these errors were encountered: