Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot Build or Run app after update

See original GitHub issue

Updated the cli and now this happens when building or quasar dev

`(node:16052) UnhandledPromiseRejectionWarning:   TypeError: Merging undefined is not supported

  - index.js:63 mergeWithOptions
    [admin]/[webpack-merge]/dist/index.js:63:19

  - index.js:52 merge
    [admin]/[webpack-merge]/dist/index.js:52:35

  - quasar-conf-file.js:392 QuasarConfFile.compile
    [admin]/[@quasar]/app/lib/quasar-conf-file.js:392:29

  - task_queues.js:95 processTicksAndRejections
    internal/process/task_queues.js:95:5

  - quasar-build:179 async build
    [admin]/[@quasar]/app/bin/quasar-build:179:3


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

downgraded and it works fine

Issue Analytics

State:
Created 2 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

afnancommented, Jun 28, 2021

Well in the future I can’t upgrade to any releases? I reported the bug to see if there is a fix and the upgrade.i did not upgrade to V3. just to ask,you say quasar is on V3 now, does this mean previous is discontinued?

On Mon, 28 Jun 2021, 11:12 pm Jeff Galbraith, @.***> wrote:

Also, quasar/app is now at v3, for quasar v2.

Since the downgrade worked for you, I am closing this ticket.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/quasarframework/quasar/issues/9846#issuecomment-869672172, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPOD4Y7O5EGMZF2I2Y4ZRLTVBYKFANCNFSM47N36ESA .

0reactions

rstoenescucommented, Jul 8, 2021

Quasar v1 -> “quasar” v1.x; “@quasar/app” v2.x Quasar v2 -> “quasar” v2.x; “@quasar/app” v3.x

“@quasar/app” has its own versioning. You can safely upgrade your packages as long as you don’t jump the major versions. Like if you are on Quasar v1, don’t jump to “quasar” v2.x or “@quasar/app” v3.x.