Skip to content
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

Bump webpack dev server to version 3.4 or above to support sockPort option #4293

Closed
tsewaiho opened this issue Jun 4, 2019 · 1 comment
Closed

Comments

@tsewaiho
Copy link

tsewaiho commented Jun 4, 2019

I use Quasar as frontend and Laravel as backend. When I am developing, I serve Laravel at 0.0.0.0:8000 and Quasar at 0.0.0.0:8080.

In the laravel view, it links to the compiled Quasar app by

<div id="q-app"></div>
<script src="http://192.168.1.3:8080/app.js"></script>

To make this approach work, I have to add sockPort:8080 in webpack dev server's option. So that the hot reload and async import know that it should use 192.168.1.3:8080 instead of 192.168.1.3:8000.

May be this page will explain better
webpack/webpack-dev-server#1792

This option is added from v3.4.0
https://github.com/webpack/webpack-dev-server/releases

@tsewaiho
Copy link
Author

tsewaiho commented Jun 4, 2019

Sorry. I am going to close this issue.
I find that there is one more problem that prevent this approach to work, Lazy loading.
sockPort still can not make the bundle to request async components from correct port.
I have to continue to use dev server proxy to develop with Laravel.

@tsewaiho tsewaiho closed this as completed Jun 4, 2019
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