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
Recently I've noticed that when generating NestJS lib, it adds this lib path twice in nx.json config.
So my questions are:
Was it really added only with recent update?
Should I add all the other libs manually now?
Why migration didn't handled it?
From what I see the idea of this "duplication" is to disable build step of typescript plugin for NestJS libs.
But other NestJS libs are still working without having entries there, so why have it?
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Recently I've noticed that when generating NestJS lib, it adds this lib path twice in nx.json config.
So my questions are:
From what I see the idea of this "duplication" is to disable
build
step of typescript plugin for NestJS libs.But other NestJS libs are still working without having entries there, so why have it?
Beta Was this translation helpful? Give feedback.
All reactions