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

Change the name field in package.json to '@WebOfTrust/signify' #205

Open
daviddm opened this issue Jan 26, 2024 · 1 comment
Open

Change the name field in package.json to '@WebOfTrust/signify' #205

daviddm opened this issue Jan 26, 2024 · 1 comment

Comments

@daviddm
Copy link
Contributor

daviddm commented Jan 26, 2024

I suggest that we change the name field from signify-ts to @weboftrust/signify.
If we want we could also claim the scope @wot to make it more developer friendly?

It is the standard in the npm ecosystem, to not add 'js', 'node', etc.
That is why i suggest to remove the ts suffix.
https://docs.npmjs.com/cli/v10/configuring-npm/package-json#name

Adding a scope gives the ability to have all future package under the same scope with short names that might already be taken in the public scope eg signify.

The project can still be called signify-ts, just not published as such.

@pfeairheller
Copy link
Member

Suggestion from @m00sey to use @keri as the scope.

@kentbull the sole dissenting vote

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