Closed talbs closed 8 years ago
If I got this right, mainly the issue happened with bower because the version mentioned in bi-app-sass
is set to 1.1.0
, and this tag is not available in the repository, right ?
if that's the case, I have just created a new tag & updated npm
registry as well.
@anasnakawa, yep! That's it. Apologies for my long way around the problem. I can verify that Bower now has the up-to-date package registered - http://bower.io/search/?q=bi-app-sass.
Thanks much!
Hi, apologies for the issue spam.
We've come across an issue with the more recent versions of bower (~1.6.5) where the version number set in a package's
bower.json
file isn't used when installing/referencing that package. We hit this when trying to set a specific version onbi-app-sass
(see https://github.com/edx/ux-pattern-library/pull/223).Here's the output from our repo's
bower.json
file ():With that in mind, here's the output when I try to run
bower install
with v1.6.5:We came across this with our Bower package recently and found that Bower now obtains and manages versions by git tags/releases. We created our first release on Github with a corresponding version number (https://github.com/edx/ux-pattern-library/releases) and our package was able to be used externally again with the
bower install
command.The same approach might be what
bi-app-sass
needs to migrate to.Let me know if you need any more info or if there's something I can do to help.