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
When I make changes to my types. Sometimes the plugin will only show/resolve TS errors/warnings after I stop and restart webpack-dev-server.
Expected behavior
The plugin would update the TS errors/warning immediately after type changes.
Steps to reproduce the issue
Don't know exactly how to reproduce, but would like to know if this is normal behavior.
Issue reproduction repository
For example
The plugin is complaining about a IS_MOBILE property that is missing from my LAYOUT type.
This is because I was experimenting a new shape for this object.
But you can see that I already removed that property from my LAYOUT interface, so that error should not be showing anymore.
Now I'm going to restart webpack:
You can see from the image above that the error is now gone.
QUESTION
Is this the normal behavior for the ForkTsCheckerWebpackPlugin? Do I need to restart my webpack-dev-server when I make those kind of changes? Or is it maybe cause because I'm using react-hot-loader or some other config I should be using. Has anyone seen this before?
NOTE: The normal VSCode ts check throughout my opened files is working fine. They always immediately reflect the changes I make to the types I'm using.
PS: Those types are declared in d.ts files using declare namespace {...}
Current behavior
When I make changes to my types. Sometimes the plugin will only show/resolve TS errors/warnings after I stop and restart
webpack-dev-server
.Expected behavior
The plugin would update the TS errors/warning immediately after type changes.
Steps to reproduce the issue
Don't know exactly how to reproduce, but would like to know if this is normal behavior.
Issue reproduction repository
For example
The plugin is complaining about a
IS_MOBILE
property that is missing from myLAYOUT
type.This is because I was experimenting a new shape for this object.
But you can see that I already removed that property from my LAYOUT interface, so that error should not be showing anymore.
Now I'm going to restart webpack:
You can see from the image above that the error is now gone.
QUESTION
Is this the normal behavior for the
ForkTsCheckerWebpackPlugin
? Do I need to restart mywebpack-dev-server
when I make those kind of changes? Or is it maybe cause because I'm using react-hot-loader or some other config I should be using. Has anyone seen this before?NOTE: The normal VSCode ts check throughout my opened files is working fine. They always immediately reflect the changes I make to the types I'm using.
PS: Those types are declared in
d.ts
files using declare namespace {...}Environment
The text was updated successfully, but these errors were encountered: