Closed abbood closed 10 years ago
interesting.. i decided to use the bower.json file of my old "functioning" angular js project.. and it worked just fine! .. so i'm guessing it has to do with some of the missing entries in the bower.json file (for example main
key perhaps? i didn't have the time for trial and error so i'll just paste my "functioning" bower.json here for future reference.. (note: i added the ionic dependency just to prove that it's not ionic's fault)
{
"name": "angular-brunch-seed",
"repo": "scotch/angular-brunch-seed",
"version": "0.3.0",
"main": "_public/js/app.js",
"ignore": [
"**/.*",
"node_modules",
"components"
],
"dependencies": {
"jquery": "~1.10.x",
"angular": "1.2.18",
"angular-sanitize": "1.2.5",
"angular-route": "1.2.5",
"angular-cookies": "1.2.5",
"angular-resource": "1.2.5",
"restangular": "1.4.0",
"angular-animate": "~1.2.x",
"angular-ui-slider": "~0.0.2",
"angular-google-maps": "https://github.com/nlaplante/angular-google-maps/archive/1832e420bd60d6f42c860f44ae40ccaf6e66aec8.zip",
"angular-easyfb": "~1.1.0",
"bootstrap-multiselect": "~0.9.x",
"ionic": "driftyco/ionic-bower#1.0.0-beta.10"
},
"overrides": {
"bootstrap-less": {
"ignore": [
"*"
]
},
"angular-mocks": {
"main": "README.md"
}
},
"resolutions": {
"angular": "1.2.18",
"angular-sanitize": "~1.2.17"
}
}
Hey @abbood,
you are using in the first example the devDependencies
which have to be explicitly included via the option includeDev
.
I used main-bower-files just fine in a previous angular project.. and now i was trying to use ionic.. so i started off using this start-up skeleton. Initially they saved all the bower components into the ./www/lib directory.. so i changed the contents of .bowerrc to
instead.. and so after running bower install all the bower folders got installed in the ./bower_components directory
for reference this is the contents of my bower.json file:
I got this in my gulpfile.coffee
but then I get this error when running
gulp bower_js
:the thing is i don't even get any debugging output before it crashes although i put the
debbuging:true
flag.. any ideas why?