Bump engine.io and karma

Bumps [engine.io](https://github.com/socketio/engine.io) to 6.2.1 and updates ancestor dependency [karma](https://github.com/karma-runner/karma). These dependencies need to be updated together.


Updates `engine.io` from 3.2.0 to 6.2.1
- [Release notes](https://github.com/socketio/engine.io/releases)
- [Changelog](https://github.com/socketio/engine.io/blob/main/CHANGELOG.md)
- [Commits](https://github.com/socketio/engine.io/compare/3.2.0...6.2.1)

Updates `karma` from 3.0.0 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/v3.0.0...v6.4.1)

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

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

QuickStart

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

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.