http-proxy-middleware TS conflict error about quasar-app-extension-ssg HOT 6 CLOSED

I pinned this issue, waiting for webpack-dev-server v4 out and updated in @quasar/app.

Thanks @IlCallo !

from quasar-app-extension-ssg.

It works! The fix seems a bit strange, if I were you I'd mark it in someway and check it again in some months to see if it can be simplified (eg. if underlying packages updates their version of http-proxy-middleware and the problems resolves itself)

Great job!

from quasar-app-extension-ssg.

@IlCallo From my understanding, there is one dependency of [email protected] in @quasar/app coming from the dependency webpack-dev-server itself.

There is another dependency of [email protected] in @quasar/cli package used by its own serve command.

The serve command of this app extension involves @quasar/app package, i think the conflict is coming from here.

from quasar-app-extension-ssg.

Exactly, and webpack-dev-server will have updated dep with version 4 (not yet out).
When webpack-dev-server v4 is out and @quasar/app updates it, you can revert back to how you were doing previously. That's why I said to mark it in some way, so you can check again in some months if the problem is solved upstream

from quasar-app-extension-ssg.

It works!

What works? What's the fix?

from quasar-app-extension-ssg.

What works? What's the fix?

@vahost The fix is to avoid using differents versions of http-proxy-middleware in your project, resulting in a types conflict.

In this App Extension i was using version [email protected] while the dependency webpack-dev-server is using the version [email protected].

from quasar-app-extension-ssg.