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

sync by install no need session #274

dead-horse opened this issue Mar 15, 2014 · 2 comments

sync by install no need session #274

dead-horse opened this issue Mar 15, 2014 · 2 comments


Copy link

@dead-horse dead-horse commented Mar 15, 2014

in the latest npm client, every update request will has a query write=true. so it is easy to separate unpublish and install.

only need to make sure all the unpublish with the latest npm client.

@dead-horse dead-horse self-assigned this Mar 15, 2014
fengmk2 added a commit that referenced this issue Mar 16, 2014
remove session access in /name and /name/version, fixed #274
@fengmk2 fengmk2 added this to the v0.3 koa milestone Mar 16, 2014
Copy link

@fengmk2 fengmk2 commented Mar 16, 2014

npm@1.4.3+ will contains ?write=true, which include in node@0.10.26+ and node@0.11.12+

Copy link
Member Author

@dead-horse dead-horse commented Mar 16, 2014

$ npm unpublish --verbose connect -f
npm info it worked if it ends with ok
npm verb cli [ 'node',
npm verb cli   '/Users/deadhorse/node_modules/.bin/npm',
npm verb cli   'unpublish',
npm verb cli   '--verbose',
npm verb cli   'connect',
npm verb cli   '-f' ]
npm info using npm@1.4.3
npm info using node@v0.11.11
npm WARN using --force I sure hope you know what you are doing.
npm verb url raw connect?write=true
npm verb url resolving [ '', './connect?write=true' ]
npm verb url resolved
npm info trying registry request attempt 1 at 13:16:44
npm http GET

we only need to make all admin users use npm@1.4.3+, so all the update request will have ?write=true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants