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 our packages can be used inside our apps
We had a typescript config via path property, for eg we could load @namespace/core from our apps/api/sample.ts
I figure out to do it via Bit with bit add packages/core --namespace "@namespace" but it seems the @ cause issue, anyway, removing the @ it seems every file become a symlink, but when I had a file into packages/core I need to bit install everytime again.
So the dev experience is worst than with typescript alias
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
-
Hello !
Regarding pnpm suggested to use Bit for monorepo deps management we are trying to figure out how to deal with current architecture of packages.
We have this
---node
-----apps
-------api
-------otherapp
-----packages
--------core
--------attr
So our packages
can
be used inside ourapps
We had a typescript config via
path
property, for eg we could load@namespace/core
from ourapps/api/sample.ts
I figure out to do it via Bit with
bit add packages/core --namespace "@namespace"
but it seems the@
cause issue, anyway, removing the@
it seems every file become a symlink, but when I had a file intopackages/core
I need tobit install
everytime again.So the dev experience is worst than with typescript alias
How to deal with that ?
Beta Was this translation helpful? Give feedback.
All reactions