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
Im using NX for years now and still can't figure out how to use it properly. Basically they say - use libs for everything, cli generates this tones of eslint and tsconfigs and i still dont know why im doing it 🤣
For example now: I have pretty giant monorepo already: few angular apps, few nest apps + few hundreds libs. Apps using crazy permissions system - many parts are lazy-loaded only for some users.
And now i want to bring Zod schemas to be sharable between NestJS and Angular apps - so i can have both types in frontend and call validation in backend and have same types. And there also will be hundreds of them eventually.
If it was just normal non-monorepo app - i would have just some folder with many files and every piece of app would just take schema it need and all that will be lazy loaded by angular in right places.
But i have monorepo... And according to this message: #3920 (comment) - i should create library for every schema that can be used separatelly 😢
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
-
Im using NX for years now and still can't figure out how to use it properly. Basically they say - use libs for everything, cli generates this tones of eslint and tsconfigs and i still dont know why im doing it 🤣
For example now: I have pretty giant monorepo already: few angular apps, few nest apps + few hundreds libs. Apps using crazy permissions system - many parts are lazy-loaded only for some users.
And now i want to bring Zod schemas to be sharable between NestJS and Angular apps - so i can have both types in frontend and call validation in backend and have same types. And there also will be hundreds of them eventually.
If it was just normal non-monorepo app - i would have just some folder with many files and every piece of app would just take schema it need and all that will be lazy loaded by angular in right places.
But i have monorepo... And according to this message: #3920 (comment) - i should create library for every schema that can be used separatelly 😢
Beta Was this translation helpful? Give feedback.
All reactions