Don't advise use of masonry.pkgd.js or flickity.pkgd.js

[desandro]

Hi there! I see in User Contributed Examples you are advising users to use masonry.pkgd.js and flickity.pkgd.js, for Masonry and Flickity. I wonder if there is a better way? These files are best used when you want to include them in a demo or page, right in a <script> or <link> tag. But they should not be uses in package managers because they include in their dependencies.

I'm not familiar with your tool, but I'd like to help. Can we recommend another solution?

I imagine part of the issue is the interpretation that bower.json's main should list all its files. Bower spec now states

The entry-point files necessary to use your package. Only one file per filetype.

See related discussions and solutions in metafizzy/outlayer#33

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/30722872-don-t-advise-use-of-masonry-pkgd-js-or-flickity-pkgd-js?utm_campaign=plugin&utm_content=tracker%2F8853550&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F8853550&utm_medium=issues&utm_source=github).