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

[HELP] Issues with re-renders #741

Closed
Bringordie opened this issue May 9, 2022 · 3 comments · Fixed by #764
Closed

[HELP] Issues with re-renders #741

Bringordie opened this issue May 9, 2022 · 3 comments · Fixed by #764
Labels

Comments

@Bringordie
Copy link

Hello,

We have a setup using yarn-workspace with babel.
When we add ForkTsCheckerWebpackPlugin out of the box to our webpack with just:
new ForkTsCheckerWebpackPlugin({ typescript: { build: true, memoryLimit: 4096, }, }),

We experience a (delayed) refresh once a file is changed. Meaning that we save, the hot reload makes a refresh instantly and add our changes, and then 3-5++ seconds later we get another refresh made by ForkTsCheckerWebpackPlugin.
Saving a component 3 times would then just que all of these refreshes, so that over a period of time all of those refreshes would go through.

We have tried to add
mode: 'readonly' which works exactly how we want. But sadly if we change another workspace we recieve no errors when there are errors. We've also tried with write-tsbuildinfo but with no luck.

Surely there is a way to have ForkTsCheckerWebpackPlugin typecheck without forcing rerenders that works across workspaces?

@piotr-oles
Copy link
Collaborator

Could you create a reproduction repository?

Bringordie pushed a commit to Bringordie/fork-ts-checker-webpack-plugin-741 that referenced this issue May 10, 2022
@Bringordie
Copy link
Author

@github-actions
Copy link

🎉 This issue has been resolved in version 7.2.13 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Successfully merging a pull request may close this issue.

2 participants