# Adding Infinite scroll to sage

**URL:** https://discourse.roots.io/t/adding-infinite-scroll-to-sage/10394
**Category:** sage
**Created:** 2017-09-09T14:15:04Z
**Posts:** 5
**Showing post:** 5 of 5

## Post 5 by @Foxaii — 2017-09-10T16:58:40Z

The ambiguity of the main property in the bower spec has lead to its use being interpreted differently over time. There’s more on the issue below:

> [@Best practice when overriding main files of bower sub-dependencies](https://discourse.roots.io/t/best-practice-when-overriding-main-files-of-bower-sub-dependencies/3590):
>
> tldr; I’m asking about best practices when installing a bower dependency which brings along it’s own dependencies. I’ve come across a bit of a problem with the Javascript bower/gulp workflow. In my example, I installed Isotope via bower install isotope --save. Now, Isotope’s bower.json has it’s main attribute set like so: "main": "js/isotope.js" , which is not actually the packaged version. That’s easy enough to override in my main bower.json: "overrides": { "isotope": { "main": ["./di…

[https://github.com/metafizzy/isotope/issues/879](https://github.com/metafizzy/isotope/issues/879)

---

_[View the full topic](https://discourse.roots.io/t/adding-infinite-scroll-to-sage/10394)._