Quasar dev -> Compiling of "UI" - error

After fresh installation of Qasar 2.0 application I encountered an error:

 App • Chaining "UI" Webpack config
 App •  WAIT  • Compiling of "UI" in progress...
(node:8208) UnhandledPromiseRejectionWarning:   TypeError: The 'compilation' argument must be an instance of Compilation
...
Use `node --trace-warnings ...` to show where the warning was created)
(node:8208) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:8208) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

To Reproduce Steps to reproduce the behavior:

1. create a project folder with Quasar CLI: $ quasar create <folder_name> --branch next
2. go to <folder_name>
3. run quasar dev
4. See error

Screenshots

Platform (please complete the following information): Quasar Version: @quasar/app Version: Dev mode… spa Pkg quasar… v2.0.0-beta.14 Pkg @quasar/app… v3.0.0-beta.18 Pkg webpack… v5 Debugging… enabled

Operating System - Windows_NT(10.0.17763) - win32/x64 NodeJs - 14.15.1

Global packages NPM - 7.5.2 @quasar/cli - 1.1.3

[rstoenescu]

Pushed a workaround for an issue in npm v7. Available in “@quasar/app” v3.0.0-beta.21 (just released it now).

[jonathanpmartins]

can confirm this is an issue with npm 7, but not with npm 6. yarn also works. i’ve tried deleting .quasar, node_modules and even my global modules, but it still didn’t work with npm 7.

I don’t thing this is a NPM 7 issue. This problem was possible introduced with the ultimate release of the beta version (remember is in development).

I have an app that worked fine until I tried to update to last beta. It broke with this same error! I think this problem was introduced in beta.16. Try to update you package.json file and force the 3.0.0-beta.15 version. Perhaps it will solve your problem!

Working with NPM 7:

"devDependencies": {
  "@quasar/app": "3.0.0-beta.15",
},

Not Working with NPM 7:

"devDependencies": {
  "@quasar/app": "3.0.0-beta.20",
},