Open atomicus opened 8 years ago
This appears to be due to a sudden repointing of ngInfiniteScroll
in bower. It now points to: https://github.com/ng-infinite-scroll/ng-infinite-scroll-bower/releases
This causes BC breaks for two reasons:
ng-infinite-scroll-npm-is-better-than-bower
If you need a quick fix you will need to point to this repo explicitly:
"ngInfiniteScroll": "git@github.com:sroze/ngInfiniteScroll#v1.0.0"
I'm not sure what the long term plan is here, because it seems like there was a revert to reclaim the name in bower here, but it isn't registered to bower yet. https://github.com/sroze/ngInfiniteScroll/commit/cedb8cb972976ebcef79900ebf32531c7734d7c0
@graingert I know the future of this project is NPM-only, but can you clarify what the recommended approach for existing bower users on previous versions is? Specifically what the plan for https://github.com/ng-infinite-scroll/ng-infinite-scroll-bower vs. https://github.com/sroze/ngInfiniteScroll is?
For now we've swetched for 1.3, but I hope this will not happen (or should I switch to npm?)
The missing tags have been pushed.
On 24 Oct 2016 14:14, "atomicus" notifications@github.com wrote:
For now we've swetched for 1.3, but I hope this will not happen (or should I switch to npm?)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sroze/ngInfiniteScroll/issues/338#issuecomment-255736714, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZQTMxnhZiJ9PhrB6LJ0QM1ESfyJg_Zks5q3K8jgaJpZM4Kerlg .
I'm currently feeling unwell so I'm afk.
On 24 Oct 2016 12:35, wrote:
Sorry, I accidentally did not upload that tag to the new repo. Try 1.
On 24 Oct 2016 12:32, "atomicus" notifications@github.com wrote:
This happened to me today:
bower ngInfiniteScroll#1.0.0 not-cached https://github.com/ng-infinite -scroll/ng-infinite-scroll-bower.git#1.0.0 bower ngInfiniteScroll#1.0.0 resolve https://github.com/ng-infinite -scroll/ng-infinite-scroll-bower.git#1.0.0 bower ngInfiniteScroll#1.0.0 ENORESTARGET No tag found that was able to satisfy 1.0.0
Whole yesterday it was working, any ideas?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sroze/ngInfiniteScroll/issues/338, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZQTArHHnz0YFeHg_WhQqlYSqmJQnimks5q3JdlgaJpZM4Kerlg .
Sorry, I accidentally did not upload that tag to the new repo. Try 1.1.0 for now?
On 24 Oct 2016 12:32, "atomicus" notifications@github.com wrote:
This happened to me today:
bower ngInfiniteScroll#1.0.0 not-cached https://github.com/ng- infinite-scroll/ng-infinite-scroll-bower.git#1.0.0 bower ngInfiniteScroll#1.0.0 resolve https://github.com/ng- infinite-scroll/ng-infinite-scroll-bower.git#1.0.0 bower ngInfiniteScroll#1.0.0 ENORESTARGET No tag found that was able to satisfy 1.0.0
Whole yesterday it was working, any ideas?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sroze/ngInfiniteScroll/issues/338, or mute the thread https://github.com/notifications/unsubscribe-auth/AAZQTArHHnz0YFeHg_WhQqlYSqmJQnimks5q3JdlgaJpZM4Kerlg .
This happened to me today:
Whole yesterday it was working, any ideas?