-
Notifications
You must be signed in to change notification settings - Fork 10
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 #1
Comments
0.2.0 was not yet covered by a bower.json file and also missing the built files. |
Hi @desandro, I fear there will be no feedback from @aurigadl. I have tried to contact the person behind since November by the email as registered for the account. And also by mentioning the name on the bower re-register comment, but also did not trigger any reaction. |
You got it. |
Jay. Thanks^Wgood :) |
hello, I have not the original project. I have stored in the repository the result of the steps and the publication of the final result and used it in bower. |
Readding this issue from @desandro as I had to recreate the repo due to git(hub) not liking it if the initial commit is redone by a forced push:
From bower/bower#120 (comment), @kossebau has requested that
viewerjs
be un-registered from aurigadl/Viewer.js. @AurigaD, it sounds like this is a legitimate request. But I'd like to see if we can get your input before I re-register the package to this repo.The
viewerjs
bower package has over 6000 hits. Switching it over to this repo could break compatibility as this repo does not have 0.2.0 and 0.2.1 releases.The text was updated successfully, but these errors were encountered: