Skip to content

Removing bad components #119

Closed
blittle opened this Issue Nov 2, 2012 · 13 comments

6 participants

@blittle
blittle commented Nov 2, 2012

If I had a component to the registry and then want to remove it. What is the process to go about doing so?

@sindresorhus
Bower member

Duplicate of #112

@paulirish
Bower member
@thanhbv
@satazor
Bower member
satazor commented Nov 3, 2012

I can also cut it down, post it here and i'll do it

@sindresorhus
Bower member

@satazor Can you add it to the readme how to go about removing a package? Maybe with a link to an ticket where they can just post the name of the package or something to be removed?

@satazor
Bower member
satazor commented Nov 3, 2012
@sindresorhus
Bower member

Thanks :)

@blittle
blittle commented Nov 4, 2012

I accidentally added the "sinonjs" component before realizing that the package.json file in the repo is incompatible with bower. Instead, I created my own proxy repo where I provide the built sinon.js component and registered it in bower as "sinon.js". To avoid confusion, maybe remove the "sinonjs" component until the author fixes/provides support for bower.

Thanks!

@satazor
Bower member
satazor commented Nov 4, 2012

@blittle done.

@davisford

Just a quick question, but if I do bower search sinon =>

Search results:

    sinon git://github.com/cjohansen/Sinon.JS.git
    sinon-chai git://github.com/domenic/sinon-chai.git
    jasmine-sinon git://github.com/froots/jasmine-sinon.git
    sinon-qunit git://github.com/cjohansen/sinon-qunit.git

..and bower search sinon.js produces no results. If I bower install sinon I get a clone of the Sinon repo at https://github.com/cjohansen/Sinon.JS which requires a build step to produce a working client-side sinon.js file -- you can't use the source directly under lib w/o building first.

So, how can I use sinon via bower? Is there another built version in the repo somewhere?

@davisford

Ok, this can be solved temporarily like this until someone creates a fork of the sinon repo that includes the built sinon.js library. The author of sinon.js (see thread linked) indicates he doesn't want to include the release library in his repo, so you may as well just delete the sinon bower project since it is not usable.

@blittle
blittle commented May 10, 2013

@davisford I created a proxy repo with the built file, but I was contacted by someone saying the repo was no longer necessary due to the official "sinon" registered in bower. I would be glad to recreate a proxy repository with the built file.

@davisford

@blittle well if you do a bower install sinon it installs the official github url repo clone, which does not contain the built sinon.js library -- only the lib source before packaging. it is unusable (e.g. try to use sinon.stub() -- not there). The link i provided above provides some context -- author decided he doesn't want the pkg/ dir in there with the generated code, so your proxy probably is needed again -- or you can just reference the sinon release url directly in your bower file (that's what i do now). That's actually a little cleaner since I don't have to yank down a whole github repo just to use a library.

@blittle
blittle commented May 10, 2013

@davisford When I get a chance I'll recreate a proxy repo, it wasn't a fork of the actual sinon repo, rather a simple repo with just the files needed for deploy (and bower file too)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.