Google Git
Sign in
apache / cordova-lib / 8371d7c1bca6b4ca6e64055054405edf8ccf11b6
commit8371d7c1bca6b4ca6e64055054405edf8ccf11b6[log] [tgz]
authorDarryl Pogue <darryl@dpogue.ca>Thu Mar 14 23:13:41 2019 -0700
committerエリス <erisu@users.noreply.github.com>Fri Mar 15 15:13:41 2019 +0900
tree0c7cd89e248e5f4f5d019deaa8fdab48561b9984
parentb5edb57b6f0e86cf3d764df1d13afa2e6833b157 [diff]
Remove saving platforms/plugins to config.xml (#750)

We've had one major version of cordova-lib that attempted to ensure both
config.xml and package.json were kept in sync, and now it's time to push
people more strongly towards using package.json.

We will still attempt to read values from config.xml and update them in
package.json, but we will no longer reflect changes back to config.xml.
Whatever's saved in package.json should always have priority over what
is read from config.xml.

The next phase will be to improve the handling of package.json updates,
and then in the next major to completely remove the code that looks at
config.xml for platforms/plugins.
11 files changed
tree: 0c7cd89e248e5f4f5d019deaa8fdab48561b9984
  1. .github/
  2. integration-tests/
  3. spec/
  4. src/
  5. templates/
  6. .eslintignore
  7. .eslintrc.yml
  8. .gitattributes
  9. .gitignore
  10. .npmignore
  11. .ratignore
  12. .travis.yml
  13. appveyor.yml
  14. CONTRIBUTING.md
  15. cordova-lib.js
  16. LICENSE
  17. NOTICE
  18. package.json
  19. README.md
  20. RELEASENOTES.md
README.md

Build status Build Status Code coverage NPM

cordova-lib

Contains npm modules used primarily by cordova and plugman.

Setup from a cloned repo

  • Clone this repository onto your local machine. git clone https://github.com/apache/cordova-lib.git
  • Install dependencies and npm-link npm install && npm link

Setup from npm

  • npm install cordova-lib

Note: you will likely also want to get github.com/apache/cordova-common, github.com/apache/cordova-create, github.com/apache/cordova-serve which previously lived in this repo but have since been moved.

npm commands

This package exposes the following commands;

  • npm run eslint - runs a linter (eslint) on relevant source and test code
  • npm run unit-tests - runs the unit tests (via jasmine) from the spec/ directory
  • npm run cover - runs istanbul code coverage tool to measure unit test code coverage
  • npm run e2e-tests - runs heavy integration tests from the integration-tests/ directory (WARNING: these take a long time to run and rely on file and network I/O)
  • npm test - shortcut for running the linter, the unit tests and the integration tests