Closed AlanJereb closed 3 years ago
Hey @AlanJereb, thanks for reporting this! I managed to reproduce it with the CRA example in this repo and pinpointed it to a bug in ForkTsCheckerWebpackPlugin
. Upgrading to the latest version and using it in the overrides seems to solve the problem. Let me know if this works for you!
Hey @AlanJereb, thanks for reporting this! I managed to reproduce it with the CRA example in this repo and pinpointed it to a bug in
ForkTsCheckerWebpackPlugin
. Upgrading to the latest version and using it in the overrides seems to solve the problem. Let me know if this works for you!
Thank you so much! You solved the issue.
Thank you for your documentation.
I'm a week and a half stuck with this problem, all my Google links are purple, and my StackOverflow questions hasn't received any answers. Maybe you will know how to solve this issue.
Using techniques from this repo everything compiles without errors, even when **common/*** (shared) code contains missing types.
Our project structure:
Root package.json
Root tsconfig.json
Root tsconfig.paths.json
common/storepackage.json - example, they are all the same, only dependencies changing
apps/web package.json
apps/web tsconfig.json
apps/web tsconfig.paths.json
We used rescripts instead of react-app-rewired, but the result is the same.
After
npm install
in the root folder, navigating into "apps/web" andnpm start
everything compiles without errors.The problem is, that if I intentionally comment out a type import inside any of
common/*
workspaces, it still compiles without errors (doesn't type check). However, doing the same insideapps/web/
throws an error for missing types. (does type check)Sorry for the long post, I really hope you can point us in the right direction.