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
I'll try and simplify my problem... if I have a monorepo with a workspace (workspace-a) and a private internal workspace (shared) that is not published.
shared is defined as a dep of workspace-a.
As shared is not published, the build for workspace-a has to bundle source from shared this means that third party dependencies used in shared have to be hoisted to workspace-a so that the package manager resolves them.
As these hoisted deps are not directly imported fallow throws them as unused deps.
I was hoping that maybe I could just ignore each hoisted dep, just for workspace-a, but it seems like the config option ignoreDependencies is scoped for the whole repo and there is not way to make the exceptions?
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.
I'll try and simplify my problem... if I have a monorepo with a workspace (
workspace-a) and a private internal workspace (shared) that is not published.sharedis defined as a dep ofworkspace-a.As
sharedis not published, the build forworkspace-ahas to bundle source fromsharedthis means that third party dependencies used insharedhave to be hoisted toworkspace-aso that the package manager resolves them.As these hoisted deps are not directly imported fallow throws them as unused deps.
I was hoping that maybe I could just ignore each hoisted dep, just for
workspace-a, but it seems like the config optionignoreDependenciesis scoped for the whole repo and there is not way to make the exceptions?Maybe I'm missing something!
Thanks in adance
All reactions