bower

I'm building a yeoman generator for simple websites. I want to include a popular JavaScript library in my scaffold. It's easy enough with bower install <mylib> . Bower then installs the library in the directory bower_components . How can configure bower to install that particular library in a particular directory? Create a file called .bowerrc in the same directory as your bower.json with the contents: { "directory": "bower" } Bower will then install all dependencies in the directory "bower" or whatever directory you specify. Hope that helps! 来源： https://stackoverflow.com/questions/19671533

When writing bower.json you can specify version numbers in your dependencies. Sometimes I see people writing { ... "devDependencies" : { "grunt" : "~0.3.13", } } What exactly does the ~ mean? Why not write >=0.3.13? Is this some sort of best practice? It's semver and the notation is the same as >=0.3.13 <0.4.0 , which will match all patch releases after and including 0.3.13 , but not 0.4.0 . This means you'll get bug fixes ( patch ), but not new features ( minor ). >=0.3.13 is not recommended as it will match anything above which will at some point break. 来源： https://stackoverflow.com

Disclaimer: I'm a node.js/grunt/bower newbie. I have a node.js/grunt/bower application that I'm trying to deploy on Heroku. Heroku builds the application as expected, but then it tries to run "npm start" which I did not specify in the package.json file. This command fails, I'm guessing because it is not a server application, and I can not see the actual application deployed in it's place on Heroku. My application can be found here: https://github.com/uzilan/sufusku So - how do I get Heroku not to run the "npm start" command, and what should it run instead? After running grunt build, the

In my package.json file, I have bower listed as a dependency. After I run npm install , bower gets installed locally. When I try to run bower after installing it locally I get an error "bower" is not recognized as an internal or external command It seems the only way to resolve this is to install bower globally. Why should I have to do this? If my project contains a local copy of bower, why won't node use it? Jimi Installing locally makes bower available to the current project (where it stores all of the node modules in node_modules ). This is usually only good for using a module like so var

What is the main Bower registry URL? We're trying to set up Bower to use our registry first, then the "official" Bower registry second. We've created our own little Bower registry based on the endpoints exposed in [bower/registry] 1 . Works great. Based on this doc , it looks like we need to create a .bowerrc file with an array of registries like { "registry": { "search": [ "http://myCustomRegistry/api", "theMainBowerRegistry" ] } } Works fine for use my custom registry, but I can't find the URL for the main Bower registry. Anyone? The default registry URL is => https://bower.herokuapp.com Now

This is driving me crazy. So far Bower+Grunt (via Yeoman) has been a major source of frustration and a waste of time. All I want is my app to use the latest (2.1.0) version of jquery. bower list correctly reported jquery 2.1.0 as an official update. I ran bower install --save jquery to update to the last version, which it did. The bower list command now correctly reports jquery#2.1.0 as a dependency, and the bower.json file now correctly lists jquery with the wanted version as a dependency: { "name": "xxx", "version": "0.0.0", "dependencies": { ... "angular": "1.2.13", "jquery": "~2.1.0",