IgniteUI
Use npm workspaces instead of yarn in the CLI
Description
We've been using yarn so that we can have multiple projects under the same repo since npm did not support that. With the addition of npm workspaces, we no longer need yarn and we can move away from it.
There has been no recent activity and this issue has been marked inactive.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
@jackofdiamond5 knowing that CodeGen will use igniteui-cli for providing empty projects and will not use it for updating routing, etc., I suggest to lower the priority of that issue and let it be closed.
@Lipata Even though the CLI will not be used to generate routing, etc, it is still a good idea to get rid of lerna/yarn and just use npm workspaces. So imo, the priority could be lowered but we should still consider including it in a future sprint as part of the CLI maintenance tasks.
There has been no recent activity and this issue has been marked inactive.