Is your feature request related to a problem? Please describe.
The current limitations of m3-h5-sdk are
that it has to be installed globally (especially for Angular) to use ng command from node_modules directory directly and
it isn't flexible enough to distinguish between standalone Angular applications/projects and Nx monorepo with multiple application/projects.
Describe the solution you'd like
I don't have a clear picture in mind for the solution. But I would provide suggestions to be more flexible and need support to understand, why the current implementation is as it is. In my opinion there were reasons to implement the current way and I need that knowledge.
Describe alternatives you've considered
Currently I don't know an alternative. We develop some applications for a client and love the reuse libraries of APIs or UI components between them in a Nx monorepo.
Additional context
I don't have additional context but I'm interested on other opinions and how do others realize M3 applications with m3-h5-sdk. How do you handle the implementation of different applications?
Is your feature request related to a problem? Please describe. The current limitations of m3-h5-sdk are
Describe the solution you'd like I don't have a clear picture in mind for the solution. But I would provide suggestions to be more flexible and need support to understand, why the current implementation is as it is. In my opinion there were reasons to implement the current way and I need that knowledge.
Describe alternatives you've considered Currently I don't know an alternative. We develop some applications for a client and love the reuse libraries of APIs or UI components between them in a Nx monorepo.
Additional context I don't have additional context but I'm interested on other opinions and how do others realize M3 applications with m3-h5-sdk. How do you handle the implementation of different applications?