Skip to content

Update package names to use scopes #531

@pcardune

Description

@pcardune

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions