Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exclude files from watching #303

Closed
deser opened this issue Jun 25, 2019 · 4 comments
Closed

Exclude files from watching #303

deser opened this issue Jun 25, 2019 · 4 comments
Labels

Comments

@deser
Copy link

deser commented Jun 25, 2019

Current behavior

I have a project with mixed js and ts files. All ts files are placed in src/ts. tsconfig is configured respectively:

"baseUrl": "src/ts",
...
"include": [
   "src/ts/**/*.ts",
   "src/ts/**/*.tsx"
], 

When I run webpack in watch mode and change something in NOT src/ts ForkTsCheckerWebpackPlugin seems still runs typechecking and linting.

I've also configure the plugin itself:

reportFiles: ['src/ts/**/*.{ts,tsx}'],
watch: 'src/ts/**/*.{ts,tsx}',

This doesn't help either.

Expected behavior

typechecking and linting in this case shouldn't run in watch mode.

Environment

all packages are latest versions

  • os: windows 10
@deser deser added the bug label Jun 25, 2019
@phryneas
Copy link
Contributor

watchPaths has apparently no effect in useTypescriptIncrementalApi: true - and I can't really think of a good way to make it work.
in useTypescriptIncrementalApi: true mode, every time webpack triggers the compile hook, all files that changed since the last trigger will be checked again.
I guess all we can do is change the documentation accordingly, what do you think @johnnyreilly ?

@johnnyreilly
Copy link
Member

Agree @phryneas - good shout 👍

@deser
Copy link
Author

deser commented Jun 25, 2019

At least something:)
Thanks guys

@piotr-oles
Copy link
Collaborator

@deser
Please try fork-ts-checker-webpack-plugin@alpha - I've published a new version which should resolve this issue 🚀
I will close this issue to clean-up the backlog. If this release didn't solve the issue, we can re-open this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants