WebStorm Bower Fundamentals

Question 1

What is Bower

Answer 1

A package installer.

Question 2

From where does Bower download its packages?

Answer 2

GitHub.com (or another git endpoint)

Question 3

What is the command for installing bower globally?

Answer 3

npm install bower -g

Question 4

What technologies do we need installed on our system to install bower?

Answer 4

Node.j’s

MSysGit/Git for Windows

Question 5

Which files can we add to control configuration of bower in our local project?

Answer 5

bower.json

.bowerrc

Question 6

What configuration options are available for bower from within the .bowerrc file?

Answer 6

directory - the directory where packages will be added.

Question 7

What is the command for installing a bower package

Answer 7

bower install [package-name]

Question 8

How do we install a specific version of a package

Answer 8

bower install [package-name]#[version]

Question 9

How do we get information about what versions of a package are available

Answer 9

bower info [package-name]

Question 10

How can we make sure that all packages are up to date

Answer 10

bower update

Question 11

How do we update just one packages

Answer 11

bower install [package-name]

Question 12

How can we check which packages are installed?

Answer 12

bower list

Question 13

How can we check what packages are available

Answer 13

bower search [search-term]

Question 14

What is the bower homepage?

Answer 14

http://bower.io

Question 15

What is the bower search page?

Answer 15

http://bower.io/search

Question 16

What is the purpose of the bower.json file?

Answer 16

1. Helps to keep track of the packages that have been installed into your project.
2. When you are going to publish your own library that can be installed by others.

Question 17

Which bower.json property tells us the package name?

Answer 17

“name”

Question 18

Which bower.json property tells us the package version?

Answer 18

“version”

Question 19

Which bower.json property tells us the file that is the main entry point for the package

Answer 19

“main”

Question 20

Which bower.json property tells us about licence information?

Answer 20

“license”

Question 21

How do we tell bower which files to ignore when the package is installed?

Answer 21

The “ignore” property in the bower.json file (a string array).

Question 22

Which properties are available to us in the bower.json file?

Answer 22

name (string), 
version (string), 
main (string or array of string), 
license (string), 
ignore (array of string), 
devDependencies (object containing properties that have a key of the package name and a value of the version of that package), 
keywords (array of string), 
dependencies (as devDependencies), 
homepage (string), 
moduleType (string)

Question 23

What is the command for creating a bower.json file?

Answer 23

bower init

Question 24

If bower is used, do we need to check in packages?

Answer 24

No!

Question 25

What is the command for installing dependent packages that are defined in the bower.json file?

Answer 25

bower install

Question 26

How do we ensure that the bower.json file is updated when we install a new package?

Answer 26

bower install [package-name] --save

Question 27

How do we ensure that the bower.json file is updated with dev dependencies when a new package is saved

Answer 27

bower install [package-name] --save-dev

Question 28

How do we ensure that a package dependency in bower.json is updated when we uninstall it?

Answer 28

bower uninstall [package-name] --save

Question 29

What is Bower Cache

Answer 29

A mechanism by which bower can locally cache packages that have already been downloaded so that it does not need to re-download them.

Question 30

How can we see what is in the bower cache

Answer 30

bower cache list

Question 31

How can we remove all items from the cache

Answer 31

bower cache clean

Question 32

How can we prevent bower from reaching out to the online registry when installing a package

Answer 32

bower install [package-name] -o

Question 33

If the package is cached, what effect does the -o flag have when installing a package?`

Answer 33

It prevents it from checking the version against the remote repository

Question 34

How can we force bower to install the files from a local git repo?

Answer 34

bower install [directory-name]

Question 35

How do we uninstall the files that have been added from a local repo?

Answer 35

bower uninstall [directory-name]

Question 36

How do we install a single file from a specific url?

Answer 36

bower install [url]

Question 37

How do we install only the dependencies (not the devDependencies) from bower.json?

Answer 37

bower install [package-name] --production

Question 38

How can we install a package into a specifically named directory (i.e. overriding the default name)?

Answer 38

bower install [directory-name]=[package-name]

Question 39

How do we get help for bower

Answer 39

bower help

Question 40

How do we get help for a specific command in bower

Answer 40

bower help [command-name]

Question 41

How do we get the git location for a specific package?

Answer 41

bower lookup [package-name]

Question 42

How do we uninstall any packages that are not listed in bower.json as a dependency and which are also not a dependency of a dependent package?

Answer 42

bower prune

Question 43

How do we reduce the output when installing a package

Answer 43

bower install [package-name] -q

Question 44

How do we pipe output from an install to a json file?

Answer 44

bower install [package-name] -j > [file-name.json]

Question 45

What is the verbose option for output

Answer 45

-V

Question 46

What is the silent option for output

Answer 46

-s

Question 47

After pushing to GitHub how do we register our package with bower?

Answer 47

bower register [package-name] [url-to-git-repo]