Per the comments about the security vulnerability warnings. The warnings don't apply to how we use those dependencies but it was easy enough to bump the version of Vue CLI we are using, which is what's causing the warning.
➜ yarn why acorn
yarn why v1.12.3
[1/4] Why do we have the module "acorn"...?
[2/4] Initialising dependency graph...
[3/4] Finding dependency...
[4/4] Calculating file sizes...
=> Found "acorn@6.3.0"
info Has been hoisted to "acorn"
info Reasons this module exists
- Hoisted from "eslint#espree#acorn"
- Hoisted from "@vue#cli-plugin-babel#webpack#acorn"
- Hoisted from "eslint-plugin-vue#vue-eslint-parser#espree#acorn"
What I tested:
The bundle js file still outputs compatible ES5 javascript for kweb as expected.
What to test:
Ensure you can still run yarn build and yarn serve commands. Ensure the app still loads in the browser.
Per the comments about the security vulnerability warnings. The warnings don't apply to how we use those dependencies but it was easy enough to bump the version of Vue CLI we are using, which is what's causing the warning.
What I tested: The bundle js file still outputs compatible ES5 javascript for kweb as expected.
What to test: Ensure you can still run
yarn buildandyarn servecommands. Ensure the app still loads in the browser.