Skip to content

Package name #1

@ghost

Description

Should the name of be "semantic-ui" instead of "semantic-ui-css"?

CLARIFICATION: I mean the "name" property in the package.json file.

This repository is a different packaging of the same underlying source code. i.e. The github endpoint is different, but the actual content is the same as the the master repo. So the name property should be the same, i.e. "semantic-ui" and not "semantic-ui-css".

Use Case: What you want to be able to do is:

bower install semantic-ui

or

bower install Semantic-Org/Semantic-UI-CSS

and still get "semantic-ui" from the Semantic-Org/Semantic-UI-CSS repository.

Otherwise, packages that consume Semantic-Org/Semantic-UI-CSS will need to specify "semantic-ui-css" in their package.json dependencies and those that consume Semantic from the master repository will need to specify "semantic-ui". It would be better if the required dependency name remained the same regardless of where the package manager sources the Semantic content. The package manager should resolve the endpoint appropriately depending on the package manager catalog.

i.e. I think the name should be semantic-ui.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions