q/app npm v7 compilation issue

Hi! I found error. I created quasar v2 project step by step from quasar v2 docs Then “cd myproject” run command “quasar dev” wait for running Error message

Dev mode… spa Pkg quasar… v2.0.0-beta.15 Pkg @quasar/app… v3.0.0-beta.20 Pkg webpack… v5 Debugging… enabled

Configured browser support (>= 87.68% of global marketshare): · Chrome for Android >= 90 · Firefox for Android >= 87 · Android >= 90 · Chrome >= 80 · Edge >= 87 · Firefox >= 79 · iOS >= 11.0-11.2 · Opera >= 71 · Safari >= 11.1

App • ⚠️ ️️Setting port to closest one available: 8081

App • Chaining “UI” Webpack config App • WAIT • Compiling of “UI” in progress… (node:3581) UnhandledPromiseRejectionWarning: TypeError: The ‘compilation’ argument must be an instance of Compilation

• NormalModule.js:181 Function.getCompilationHooks [qs-v2-2]/[webpack]/lib/NormalModule.js:181:10

• pluginWebpack5.js:37 [qs-v2-2]/[vue-loader]/dist/pluginWebpack5.js:37:26

• Hook.js:14 Hook.CALL_DELEGATE [as _call] [qs-v2-2]/[tapable]/lib/Hook.js:14:14

• Compiler.js:1017 Compiler.newCompilation [qs-v2-2]/[app]/[webpack]/lib/Compiler.js:1017:26

• Compiler.js:1059 [qs-v2-2]/[app]/[webpack]/lib/Compiler.js:1059:29

• Hook.js:18 Hook.CALL_ASYNC_DELEGATE [as _callAsync] [qs-v2-2]/[tapable]/lib/Hook.js:18:14

• Compiler.js:1054 Compiler.compile [qs-v2-2]/[app]/[webpack]/lib/Compiler.js:1054:28

• Watching.js:134 [qs-v2-2]/[app]/[webpack]/lib/Watching.js:134:19

(Use node --trace-warnings ... to show where the warning was created) (node:3581) 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:3581) [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.

Thanks

[rstoenescu]

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

[rstoenescu]

Hi All,

Best practice (and sorry for the caps): ALWAYS READ THE RELEASE NOTES (especially while we’re on beta).

I specifically wrote that you might need to delete node_modules and yarn.lock/package-lock.json files because of NPM/Yarn not correctly updating its cache. This is not a Quasar issue and you DON’T need to create a new project to port your current one over.

You’re not forced to use Yarn, but from our own experience over the years, it manages the dependencies far better, which is why we recommend it. At the end of the day, NPM and Yarn are just tools to help you install the necessary packages being used by your app. Does a package manager really matter more than your productivity and your app’s features?

It really saddens me to read about these problems caused by external tools and Quasar getting the hammer for them.

Please report back if deleting node_modules AND yarn.lock/package-lock.json THEN yarn/npm installing does not fixes the problem for you.