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
Bower registration #5
Comments
Hi, There should be a bower.json file there: this is clearly a mistake from my part: bower.json is there on a tag version but doesn't appear on the master branch https://github.com/warpdesign/deferred-js/tree/v1.0.3) : this will be fixed. As for the different source directory: this has been changed by @iam4x who forked my repository. Deferred-js is currently known as deferred-js in GitHub and Npm: I really would like to keep the same name for each registry it is available on. Is there really nothing that can be done ? Thank you. |
@iam4x Would you be okay with un-registering your fork as |
I have added missing bower.json file. |
Hello @desandro @warpdesign, tell me when you want to switch. I'm okay with it, but let's do it in the same hour together so we don't break projects depending on it. |
@iam4x Thanks for your cooperation. Can you please unregister |
I hadn't noticed your messages, sorry about that. |
@warpdesign Sorry didn't see, I did unregister the package today. |
I have registered it as deferred-js, thanks @iam4x ! |
Hi there! I'm moving discussion from bower/bower#120 (comment) over here. Thanks for looking into adding bower support.
deferred-js
is currently registered to iam4x/deferred-js-bower. It is a port of this repo, but I don't feel comfortable switching it over./deferred.js
vs/js/deferred.js
bower.json
I feel the best solution is to register this repo under a different name, like
standalone-deferred
or even justdeferred
. This way, we don't break compatibility withdeferred-js-bower
.The text was updated successfully, but these errors were encountered: