bootstrapworld
Update package names to use scopes
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
- @bootstrapworld/codemirror-blocks
- @bootstrapworld/wescheme-blocks
- @bootstrapworld/pyret-blocks
- @bootstrapworld/blocks-toolkit
etc.
What do you think @schanzer?
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?
The package scopes/names are unrelated to what repos the source code is in.