Skip to content
This repository has been archived by the owner on May 17, 2023. It is now read-only.

Naming cosmos 馃槗 #38

Closed
siddharthkp opened this issue Dec 11, 2017 · 6 comments
Closed

Naming cosmos 馃槗 #38

siddharthkp opened this issue Dec 11, 2017 · 6 comments

Comments

@siddharthkp
Copy link
Contributor

siddharthkp commented Dec 11, 2017

cosmos and @cosmos are both taken on npm (Related: #3)

Also, @dschenkelman suggested that we make sure we are not infringing any copyrights

@landitus
Copy link
Contributor

The initial naming is meant as a 'codename' for the project, to use it internally. But ideally it's a good name for the public face of the project as well.

@siddharthkp
Copy link
Contributor Author

I like the name, but I also want people to be able to do

> npm install cosmos

and

import { Button } from 'cosmos'

which they can't 馃様

@landitus
Copy link
Contributor

landitus commented Dec 11, 2017

What about auth0-cosmos, should we at least save it from the npm registry for now?

@siddharthkp
Copy link
Contributor Author

siddharthkp commented Dec 11, 2017

published empty auth0-cosmos

Also, we always have the option of @auth0/cosmos as the last resort 馃槃 Doesn't look as pretty as just cosmos but almost there

@hzalaz
Copy link
Member

hzalaz commented Apr 3, 2018

馃檹 use @auth0/cosmos

@siddharthkp
Copy link
Contributor Author

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants