Skip to content
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: how to get masonry packaged version? #484

Closed
pajooh opened this issue Jan 27, 2014 · 4 comments
Closed

bower: how to get masonry packaged version? #484

pajooh opened this issue Jan 27, 2014 · 4 comments

Comments

@pajooh
Copy link

pajooh commented Jan 27, 2014

masonry.pkgd.js or masonry.pkgd.min.js

@desandro
Copy link
Owner

Hi! Thanks for reporting this issue. Bower will not provide packaged version as it provides all the dependencies. See my comment in metafizzy/packery#12

@am
Copy link

am commented Feb 24, 2014

@desandro I guess that what @pajooh means is that when we use bower (in the README you reference this has a way to install masonry) there is no access to the packed version.
This may mislead people in error, as there are many other projects that make the packaged file available so we can have the populate our project bower file with the dependencies, do bower install and then serve the files directly from bower_components.

@seiyria
Copy link

seiyria commented Mar 5, 2014

This definitely had me confused until I came here to take a look. It would be nice to have a dist/ folder that just contained the distribution of masonry.

desandro added a commit that referenced this issue Mar 15, 2014
@desandro
Copy link
Owner

Packaged files are now committed in dist/, starting with v3.1.5. https://github.com/desandro/masonry/tree/master/dist

Closing as fixed! ⚡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants