Bump axios and karma

Removes [axios](https://github.com/axios/axios). It's no longer used after updating ancestor dependency [karma](https://github.com/karma-runner/karma). These dependencies need to be updated together.


Removes `axios`

Updates `karma` from 2.0.2 to 6.4.1
- [Release notes](https://github.com/karma-runner/karma/releases)
- [Changelog](https://github.com/karma-runner/karma/blob/master/CHANGELOG.md)
- [Commits](https://github.com/karma-runner/karma/compare/v2.0.2...v6.4.1)

---
updated-dependencies:
- dependency-name: axios
  dependency-type: indirect
- dependency-name: karma
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
3 files changed
tree: f4bccbd8c6c1d2b9ffe860457e96a23a92fc94ce
  1. .github/
  2. e2e/
  3. scripts/
  4. src/
  5. .angular-cli.json
  6. .angulardoc.json
  7. .dockerignore
  8. .editorconfig
  9. .gitignore
  10. CONTRIBUTING.md
  11. Dockerfile
  12. karma.conf.js
  13. LICENSE
  14. license.config.js
  15. NOTICE
  16. package-lock.json
  17. package.json
  18. protractor.conf.js
  19. proxy.conf.json
  20. README.md
  21. tsconfig.json
  22. tslint.json
  23. yarn.lock
README.md

Fims QuickStart Build Status Docker Build

Setup

  • Ensure you have Node 6.10.0+ and NPM 3+ installed.
  • Install Node packages npm i

Development

Production build

  • Run license check npm run checkLicenses
  • Run in production mode npm run runProd. This is only to test if AOT is working and should never be used in a production environment.
  • Build production assets npm run build. Files will be stored under /dist.

Tests

  • Please follow the best practices here Angular Testing
  • Run karma tests npm run test

Running from Docker container

See https://github.com/apache/fineract-cn-docker-compose for running all the Fineract-CN services from Docker.

Versioning

The version numbers follow the Semantic Versioning scheme.

In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.

  • snapshot - A release currently in development.
  • m - A milestone release include specific sets of functions and are released as soon as the functionality is complete.
  • rc - A release candidate is a version with potential to be a final product, considered code complete.
  • ga - General availability indicates that this release is the best available version and is recommended for all usage.

The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:

1.2.3-snapshot
1.3.5-m.1
1.5.7-rc.2
2.0.0-ga

Contributing

See CONTRIBUTING file.

License

See LICENSE file.