You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: