Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update package names to use scopes #531

Open
pcardune opened this issue Oct 25, 2021 · 3 comments
Open

Update package names to use scopes #531

pcardune opened this issue Oct 25, 2021 · 3 comments
Milestone

Comments

@pcardune
Copy link
Collaborator

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?

@pcardune pcardune added this to the beta-1 milestone Oct 25, 2021
@schanzer
Copy link
Member

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?

@pcardune
Copy link
Collaborator Author

The package scopes/names are unrelated to what repos the source code is in.

@schanzer
Copy link
Member

Perfect. Then I'm in firm agreement!

@pcardune pcardune changed the title Decide on package naming and whether to use scopes Update package names to use scopes Oct 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants