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
In order to reuse/build upon this prototype-frontend implementation in other application repositories, we need to split up the code base into multiple separate packages that can be imported using npm/yarn. A so called monorepo approach prevents us from having a number of interlinked repositories.
Many other libraries (like Angular itself) have this in place. These are the Angular packages that are published on npmjs. E.g. the @angular/core
This issue is about selecting a tool and setting it up in our repo
A couple of tools I found and discussed with a colleague:
Context
In order to reuse/build upon this prototype-frontend implementation in other application repositories, we need to split up the code base into multiple separate packages that can be imported using npm/yarn. A so called monorepo approach prevents us from having a number of interlinked repositories.
Many other libraries (like Angular itself) have this in place. These are the Angular packages that are published on npmjs. E.g. the @angular/core
This issue is about selecting a tool and setting it up in our repo
A couple of tools I found and discussed with a colleague:
The text was updated successfully, but these errors were encountered: