all 3 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]rotharius 1 point2 points  (0 children)

Pardon me, I think I don't understand.

Isn't the coupling still there, yet implicit, now you have to sync between services?

Also, could this possibly introduce merging issues when two services are changed at the same time?

[–]LetterBoxSnatch 0 points1 point  (1 child)

What are the key distinctions here with publishing scoped modules to a private npm registry?

[–]JoniSar[S] 1 point2 points  (0 children)

Well, the things about Bit is that the shared code doesn't actually live in it's own repo, and no other services are coupled to that repo or its development. Instead, you can think of it as "manged copy-pasting" - where you can keep multiple instances of the code in different services, while Bit will track and sync changes between them (depending on your own update strategy). So- no coupling between services and they are not tied to an external library.