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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mickey-bimlive opened this issue Apr 26, 2025 · 0 comments

Comments

@mickey-bimlive
Copy link

mickey-bimlive commented Apr 26, 2025

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant