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
So I have a monorepo using yarn 3.x workspaces and there's a package with webpack that depends on another package which is symlinked through yarn. The problem is that while a webpack dev server is running if I re-build that linked dependency, fork-t-schecker-webpack-plugin is no longer able to find that dependency, even after the linked rebuild has finished and there are definitely files there.
The error above is being thrown even though @speckle/viewer (a linked package) has already been rebuilt and definitely exists at that point.
Expected behavior
After the linked package finishes rebuilding, fork-ts-checker-webpack-plugin should clear out its cache and re-evaluate whether the previously missing module and its types are still missing. They aren't, so it should pick up on that and stop reporting an error that no longer exists.
Current behavior
So I have a monorepo using yarn 3.x workspaces and there's a package with webpack that depends on another package which is symlinked through yarn. The problem is that while a webpack dev server is running if I re-build that linked dependency, fork-t-schecker-webpack-plugin is no longer able to find that dependency, even after the linked rebuild has finished and there are definitely files there.
The error above is being thrown even though @speckle/viewer (a linked package) has already been rebuilt and definitely exists at that point.
Expected behavior
After the linked package finishes rebuilding, fork-ts-checker-webpack-plugin should clear out its cache and re-evaluate whether the previously missing module and its types are still missing. They aren't, so it should pick up on that and stop reporting an error that no longer exists.
Issue reproduction repository
Here's a reproduction link: specklesystems/speckle-server#889
Steps to reproduce the issue
Environment
package.json
] 8.11.0package.json
] 4.46.0The text was updated successfully, but these errors were encountered: