Using bower: Install bower: npm install -g bowerĪnd then go to your project folder and install ngCordova in it: bower install -save ngCordova Using npm: Go to your project folder and install ng-cordova in it: npm install -save ng-cordova I don't know what variant is more fit for you, it depends on the package manager you want to use for the client side. What about ngCordova: you can install it using npm or bower. Using npm install ionic: npm install -g ionic Thanks to for pointing to the correct way (look at the comment bellow). You may want to upgrade it to the latest version: $ npm install -g Previous version was npm update -g npm. Npm is shipping with node (or iojs), so it will be available after installing node (or iojs). Using nvm install node or iojs (you can install any version you want): nvm install 0.10
If you have trouble with installing nvm using brew you can install it manually (see here) profile run: echo "source $(brew -prefix nvm)/nvm.sh" > ~/.profile zshrc file to not run it again on every terminal start. The one exception to the above is that version numbers with a major version of 0 don’t have a stable API, so going from 0.0.1 to 0.0.2 could be breaking-as could going from 0.1.0 to 0.2.0.Ī caret ^ before a version number means that our code depends on any version compatible with that number-for example, if we had a dependency "foo": "^1.4.0", our code should work with any versions between 1.4.0 and 2.0.0, such as 1.4.1 or 1.11.2.Add the last command to the.
Patch version changes mean that bugs have been fixed-if we switch from 1.0.8 to 1.0.7, our code may stop working because of the bug that was fixed in patch version 8.
Minor version changes mean that functionality has been added-if we write our code using version 1.4.0, it may break if we switch to version 1.3.0, because it may use a feature introduced in minor version 4. (For example, if the library renamed doThis to doThat, and our code were still called doThis(), we’d get an error.) Minor and patch version changes do not break the API-if we write our code using version 1.0.0 of a library, we can safely upgrade to version 1.0.8 or 1.4.0. Major version changes mean the library’s API has been changed in an incompatible way-if we write our code to use version 1.0.0 of a library (for example, using the library’s function doThis()), our code will probably break if we switch to version 2.0.0. npm packages follow SemVer, a convention for version numbering:
We see the current package’s version, which was 0.13.1 at the time of writing.
0 kommentar(er)
