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
{{ message }}
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
Second option seems more appropriate to run set of UI's together, however, to do that we need to unify how we run projects in the dev. kas-ui, kafka-ui have different scripts to start in dev mode thus it is not possible to issue same script on those etc.
WDYT?
Alternatively we can have script that allow us to define dev profiles in package.json (list of projects that will be started in dev mode etc.
The text was updated successfully, but these errors were encountered:
Yeah, I don't think we are ready to align all the dependencies for the projects.
The issue is that start:dev doesn't work on kas-ui for running federated because of ports. What about just using https://github.com/mysticatea/npm-run-all as then you can specify each module separately.
Or add a new target to each project like run:federate that is just a link to start:dev?
We have all remote repositories in modules folder right now. Those will have separate node_modules installed at the time of setup.
We can add:
Second option seems more appropriate to run set of UI's together, however, to do that we need to unify how we run projects in the dev. kas-ui, kafka-ui have different scripts to start in dev mode thus it is not possible to issue same script on those etc.
WDYT?
Alternatively we can have script that allow us to define dev profiles in package.json (list of projects that will be started in dev mode etc.
The text was updated successfully, but these errors were encountered: