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

[Next 9.0.0] How to disable ForkTsCheckerWebpackPlugin? #7809

Closed
rwu823 opened this issue Jul 8, 2019 · 5 comments
Closed

[Next 9.0.0] How to disable ForkTsCheckerWebpackPlugin? #7809

rwu823 opened this issue Jul 8, 2019 · 5 comments

Comments

@rwu823
Copy link

rwu823 commented Jul 8, 2019

Is it supported?

@Timer
Copy link
Member

Timer commented Jul 8, 2019

Not currently -- you cannot disable ForkTsCheckerWebpackPlugin.

Do note type checking happens in the background so it does not affect the reload/rebuild speed of your project.

If you're finding yourself constantly hitting typescript errors maybe try using strict: false in your tsconfig.json.

@Timer Timer closed this as completed Jul 8, 2019
@iamawebgeek
Copy link

iamawebgeek commented Aug 7, 2019

@Timer have the same request. For me ts checking plugin eats too much memory and CPU on every hot reload, and I still have editor typescript checker, so I don't need another one. An option to disable ForkTsCheckerWebpackPlugin on dev would be awesome

@kachkaev
Copy link
Contributor

kachkaev commented Aug 7, 2019

You can find a workaround in #7687 (comment)

I also hope that an official option will be possible in future.

@Timer
Copy link
Member

Timer commented Aug 11, 2019

Please see #8331.

@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants