* chore(project): bump @babel/cli from 7.12.1 to 7.15.4
* chore(project): bump @babel/core from 7.11.6 to 7.15.5
* chore(project): bump @babel/plugin-proposal-class-properties to 7.14.5
* chore(project): bump @babel/plugin-transform-runtime to 7.15.0
* chore(project): bump @babel/preset-env from 7.11.5 to 7.15.4
* chore(project): bump @babel/preset-typescript from 7.10.4 to 7.15.0
* chore(project): bump babel-loader from 8.1.0 to 8.2.2
* chore(project): bump babel-plugin-module-resolver from 4.0.0 to 4.1.0
* chore(project): bump @popperjs/core from 2.4.4 to 2.10.1
* chore(project): update babel.config.js
* chore(project): update jest.config.js
* chore(project): bump @typescript-eslint/eslint-plugin to 4.30.0
* chore(project): bump @typescript-eslint/parser from 4.29.3 to 4.30.0
* chore(project): bump algoliasearch from 4.4.0 to 4.10.5
* chore(project): bump transliteration from 2.1.11 to 2.2.0
* chore(project): bump typescript from 4.3.5 to 4.4.2
* chore(project): bump esbuild from 0.12.5 to 0.12.25
* chore(project): bump file-loader from 6.1.0 to 6.2.0
* chore(project): bump rollup from 2.28.2 to 2.56.3
* chore(project): bump rollup-plugin-esbuild from 4.2.3 to 4.5.0
* chore(project): bump sass from 1.37.0 to 1.39.0
* chore(project): move sass & typescript to devDependencies
* fix: stop pinning vue peer dependency version
It should be safe to trust `vue` to follow semver.
Pinning a peer dependency version is a bad idea because any change in
peer dependency requirement should be considered a breaking change in
theory.
On the other hand, `@vue/compiler-sfc` has a strict peer dependency
version requirement.
So pinning the `vue` version is likely to causing issues like
https://github.com/vitejs/vite/issues/4573 in the future.
* chore: update lockfile
* bumping version
* build(core): bumping vue version
- Bumping up vue version from ^3.0.0 to ^3.0.3 due to the change of `emitOptions`
* Remove transition mock/Add before-enter and before-leave hook emitter for popper
