vue@3.0.8
introduced an existence check forSVGElement
in@vue/runtime-dom
. This brokejsdom
as it didn't have a reference toSVGElement
. The Vue core team fixed this invue-cli
. This patch brings that fix into our mochapacksetup.js
. For context, please see the original issue.
- Update to Vue 3.
- Update vue-test-utils to ^2
- Add ability to pass in reporter for code coverage
- Add/refactor unit tests
- Add a simple logger
- Allow overriding of
.nycrc
. If a local.nycrc
is present, it will use that instead of default.nycrc
.
- Ensuring client uses .nycrc config from @rei/vunit. This fixes issue of no src files being reported during coverage run.
- Include .vue, .js extensions
- Exclude test/ directory
- Switching from mocha-webpack to mochapack due to lack of maintenance now on mocha-webpack.
- See
- Enabling async/await in client mocha unit tests via babel config in webpack.conf.
- Updating mocha to v8.
- Updating @babel dependencies.
- Adding .eslintrc.json
- Updating dependencies causing security vulnerabilities.
- Breaking changes:
- Replaces expect with chai.expect.
- Potentially breaking change is
@vue/test-utils
peer dependency which was updated from 1.0.0-beta25 to 1.0.0-beta31. This is installed in alongside ofvunit
and does not require an update but if you did update it, you may see breakages due to breaking changes withinvue/test-utils
. Refer to the @vue/test-utils CHANGELOG for the specific breaking changes.
- Pull in babel config for client test coverage. Clients no longer need to provide this in local
.babelrc
orpackage.json
. - Making
@rei/test-utils
a peer dependency. - Updating and/or removing unneeded dependencies.