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
A lot of projects that ship multiple npm pakages will put all their packages under the same npm scope. Even the new version of codemirror is doing this. I think we should probably do the same, but I'm wondering what the scope should be.
The scope should ideally (IMO) be the name of some organization that manages all the packages, so we could have
That makes perfect sense to me. But I thought the toolkit would be part of the cmb repo? Or do these naming conventions exist independently of whether a package is inside a monorepo or not?
A lot of projects that ship multiple npm pakages will put all their packages under the same npm scope. Even the new version of codemirror is doing this. I think we should probably do the same, but I'm wondering what the scope should be.
The scope should ideally (IMO) be the name of some organization that manages all the packages, so we could have
etc.
What do you think @schanzer?
The text was updated successfully, but these errors were encountered: