Hi,

Is it a bad idea to lazy-load just one component when navigating to a different url?
The lazy-loading docs just mention pages, but not sure if we can interpret that as component as well.

Thank you.

You can try disabling cache for the browser while you’re in development.

Hi,

I currently switched over to lazy-loading my components following the quasar guide on lazy-loading.

However, when I refresh my page in the route ‘/dealerships’, and then try to navigate to the path ‘/’, I get these errors:

I think the problem is webpack is trying to load the chunk from the wrong url. Does anyone know how to fix this?

[EDIT] So, I think the problem lies with the browser making a server call first everytime I reload or visit a new route and since I’m doing quasar dev I don’t have a server to handle these endpoints. Is there way I can handle this just using quasar dev?

Thank you!

Hi,

Does quasar webpack come pre-installed with the splitChunks option? If not, how would I configure webpack in quasar.conf.js to enable it?