Skip to content

Quasar Dev Build fails due to Webpack issue after upgrade of QMarkdown from v2.0.0 Beta 10 to v2.0.5 #409

@mickey-bimlive

Description

@mickey-bimlive

I'm using QMarkdown with the following Quasar levels:

 Dev mode.................. spa
 Pkg quasar................ v2.18.1
 Pkg @quasar/app-webpack... v3.15.1
 Pkg webpack............... v5
 Debugging................. enabled

A couple of days ago I realized that QMarkdown is still on v2.0.0 Beta 10. So (maybe naively), I issued:
quasar upgrade -i

Initially that upgrade looked successful:

@quasar/extras: 1.16.9 → 1.16.17
@quasar/quasar-app-extension-qmarkdown: 2.0.0-beta.10 → 2.0.5

However, when I tried quasar dev after that upgrade, my dev build fails with the following error message:
App • ⚠️ Extension(@quasar/qmarkdown): is not compatible with @quasar/app-webpack v3.15.1. Required version: ^4.0.0

Reading https://quasar.dev/quasar-cli-webpack/upgrade-guide, upgrading a Quasar app to Webpack v4 looks like complicated work.

Is it true that I need to do that, only to be able to upgrade the QMarkdown app extension to the newest level?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions