-
Notifications
You must be signed in to change notification settings - Fork 13
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
Rename seshat-node package #9
Comments
There is already a package on npm called |
Hmm... I am tempted to say we should create an org and have a scoped package then. That would communicate the purpose more clearly without redundant words. I'll raise the idea and see where it takes us. |
Alternatively, we could go with a less obscure name like |
Eh, I'm kinda fond of the Seshat name especially since we did get the |
Ah yes, |
Ok, I'll rename it to |
It seems a bit strange for the package on npm to be called
seshat-node
... The node bit is quite redundant, since that's why it's on npm in the first place.Have a directory
seshat-node
seems fine, but it'd be nice to change the package name inpackage.json
so that it feels more natural to use.The text was updated successfully, but these errors were encountered: