-
Notifications
You must be signed in to change notification settings - Fork 547
bower main property not valid #157
Comments
+1 would love to see this fixed (updated). |
+1 |
+1 |
I also recently opened an issue related to Bower. There seems to be a few fixes necessary related to Angular-UI with Bower. I think they should be on a higher priority considering Yeoman uses While I think I can fix most of these issues, given that it's package manager related, I think we really need approval from the repo/package owners before any of us can make pull requests. |
+1 wish to see it fixed |
+1 |
1 similar comment
+1 |
+1 |
+42 |
The workaround for this is to install the master branch with:
|
I finally took the time to do it... I added a `bowerData` key to the client publishers to overwrite any existing bower properties in the built output (we you run `grunt build:bower`). This fix exits in `[email protected]` and `[email protected]` so old and new repos can use it. Closes #177, #161, #157
UI.Utils modules was split in individuals repositories. If still valid, please consider re-submitting the issue on its dedicated issue tracker. See the README for details. |
i use ui-utils via bower, and the modules folder is not included in bower
so,
"main": "./modules/utils.js"
is not validThe text was updated successfully, but these errors were encountered: