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

Issue with angular-cache package #2

Open
thany opened this issue Jan 5, 2015 · 2 comments
Open

Issue with angular-cache package #2

thany opened this issue Jan 5, 2015 · 2 comments

Comments

@thany
Copy link

thany commented Jan 5, 2015

If I install angular-cache:

bower install angular-cache

It'll install angular as well, so all good. Then if I copy the things to a test directory:

bower-copy --dest ./test

The test directory ends up containing angular.js (non-minified) and angular-cache.js (minified).

The problem is that all files ending up i the dest directory are non-minified except angular-cache. Perhaps angular-cache isn't configured correctly, but I have no idea. In any case it'd be nice to either have all dest files always non-minified, or always minified (with an option perhaps, and appending .min to the filename), or append .min to files that are going to end up minified instead of non-minified.

So it's inconsistent. Which in my particular case means that my deployment chain cannot determine which files are already minified and which ones still need minification.

@thany
Copy link
Author

thany commented Jan 5, 2015

Actually, there's another package that doesn't work well with bower-copy:

bower install markdown-js

Doesn't get copied at all.

@dotnetCarpenter
Copy link

@thany This probably due to the 2 bower.json files in angular-cache and angular respectively. You'll get whatever they have marked as main in bower.json.

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

2 participants