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
{{ message }}
This repository has been archived by the owner on Jun 2, 2024. It is now read-only.
$ 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 [email protected]
npm info using [email protected]
npm WARN using --force I sure hope you know what you are doing.
npm verb url raw connect?write=true
npm verb url resolving [ 'https://registry.npmjs.org/', './connect?write=true' ]
npm verb url resolved https://registry.npmjs.org/connect?write=true
npm info trying registry request attempt 1 at 13:16:44
npm http GET https://registry.npmjs.org/connect?write=true
we only need to make all admin users use [email protected]+, so all the update request will have ?write=true
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
in the latest npm client, every update request will has a query
write=true
. so it is easy to separateunpublish
andinstall
.only need to make sure all the
unpublish
with the latest npm client.The text was updated successfully, but these errors were encountered: