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
So to start I am working on an NX react project that has about 5 apps and like 20 libraries in our repo. We currently have them split by the tenant app (this is a logical seperation for things like components, services and themes that are specific to the different tenants we build apps for)
For the apps and libs everything makes sense, but we have made each libs/tenant folder into its own project that has a storybook instance that encompasses all the nested components and libs within that tenants folder structure.
We do this because all the components under a tenant share the same themes and we need to publish the storybook for that tenant in a location that designers can view.
The Issue we have seen is that this grouping project that we use now is depended on whenever a child is depended on, and that causes little changes in libs that might only rerun appA to rerun all apps tied to a tenant.
The discussion i am putting here is because
i wanted to see if this made sense or if i was doing this wrong
if it was possible to set these projects so that no other app or lib is dependent on them.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Howdy,
So to start I am working on an NX react project that has about 5 apps and like 20 libraries in our repo. We currently have them split by the tenant app (this is a logical seperation for things like components, services and themes that are specific to the different tenants we build apps for)
Something like this
For the apps and libs everything makes sense, but we have made each
libs/tenant
folder into its own project that has a storybook instance that encompasses all the nested components and libs within that tenants folder structure.We do this because all the components under a tenant share the same themes and we need to publish the storybook for that tenant in a location that designers can view.
The Issue we have seen is that this grouping project that we use now is depended on whenever a child is depended on, and that causes little changes in libs that might only rerun appA to rerun all apps tied to a tenant.
The discussion i am putting here is because
Beta Was this translation helpful? Give feedback.
All reactions