-
-
Notifications
You must be signed in to change notification settings - Fork 771
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
Proposal: publish to npm using scopes #1652
Comments
Yes that would be nice and consistent with GitHub. It also gives us more freedom with naming future modules 👍 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
How do we notify people of the naming change? Most people are probably used to adding sinon to a project using |
I think we should communicate as soon as possible with a note on the website/documentation and the
Furthermore we should publish a deprecation notice on npm, e.g. CoffeScript is doing this: When you run I have no experience with npm but,
😄 I like this. When we log a message everytime sinon is |
Deprecating packages is not that difficult, I've already done it when we adopted |
Issue for nise: sinonjs/nise#77 |
This is only missing for sinon. |
I think it would make sense to start using scopes when we publish things to npm.
sinon
=>@sinonjs/sinon
nise
=>@sinonjs/nise
lolex
=>@sinonjs/lolex
sinon-test
=>@sinonjs/sinon-test
,@sinonjs/test
,@sinonjs/testcase
or some other nameThe text was updated successfully, but these errors were encountered: