I think this is a duplicate React problem Current behavior : In the container project, it works fine when I route to sub-app/foo. But when I route to sub-app I get the following error : Notice: sub-app/foo will get a class component. sub-app will get a React hooks component Expected behavior: The result I expect is that the subApp code
Tag: lerna
How to upgrade node module of the lerna’s subpackage
I started using lerna to be able to install all node modules for all sub packages using a single command. At the moment I do not use any other lerna features except lerna bootstrap. My lerna.json: my root package.json: my package-a’s package.json: my package-b’s package.json: i want to upgrade moment in the package-b. if i run yarn upgrade moment –latest
Webpack resolve alias and compile file under that alias
I have project which uses lerna ( monorepo, multiple packages ). Few of the packages are standalone apps. What I want to achieve is having aliases on few of the packages to have something like dependency injection. So for example I have alias @package1/backendProvider/useCheckout and in webpack in my standalone app I resolve it as ../../API/REST/useCheckout . So when I
How Should VSCode Be Configured To Support A Lerna Monorepo?
I have a lerna monorepo containing lots of packages. I’m trying to achieve the following: Ensure that VSCode provides the correct import suggestions (based on package names, not on relative paths) from one package to another. Ensure that I can ‘Open Definition’ of one of these imports and be taken to the src of that file. For 1. I mean