brisk agate
❗️ Expect significant performance loss in development.
❗️ Disabling the browser's cache results in waterfall requests.
How can we get rid of them? And why Qwik is so slow? Is it related to those lines? And why the HMR does not work and we end up with complete page reload for each change?
dire lion
A lot of the optimizations are at build time. This message is just a reminder. In the latest version it was made less scary
Hot reload is complex because of the segmentation, we didn't get around to it yet
And in many cases there's nothing to reload because the component code isn't on the client
brisk agate
@dire lion but that makes the development process extremely unpleasant. For a real website like osouli.trade, for each simple change it takes like 5 seconds to reload. That makes a huge difference for somebody like me who is used to constantly hit Ctrl+S. Is it going to become betteri n the future? What options do we have for that? And sometimes we go behind the VPN and that 5 seconds become 20 seconds.
dire lion
<@105886181710913536> but that makes the development process extremely unpleasan...
Interesting, what is that time being spent on?
brisk agate
reloading. A simple change, and the browser tab goes into a complete reload mode. And let me check to see what takes the most time.
dire lion
Qwik is way faster than that so likely you can add caching to your loaders
brisk agate
I recorded a video. 15 MB. How can I send it to you? The main problem seems to be related to the Tailwind. But after that there is still problems.
dire lion
I'm on my phone
So things to check in the devtools:
If the html takes a long time, figure out what in the server is slow. You can run the server in the inspector and run performance on it to see where time is being spent
Tailwind should be V4, big improvements
If afterwards takes a long time, figure out what, with the network and performance tabs
If you're loading data, be sure to cache it somewhere
brisk agate
I reported the issue to the Tailwind team. That's for the Tailwind part.
https://github.com/tailwindlabs/tailwindcss/issues/16565
Let me first fix this part form Tailwind. Then we will continue the Qwik part. Thank you for now.
silk zephyr
@brisk agate if your dev server is slow, try setting qwikVite({ lint: false }) in your vite config.
silk zephyr
For more info: https://github.com/QwikDev/qwik/issues/6837
brisk agate
@silk zephyr I'm still waiting for the Tailwind problem to get solved. Then I will test this. Because Tailwind's problem is so bad I can't confirm if this config works or not.
silk zephyr
<@465872008786346014> I'm still waiting for the Tailwind problem to get solved. ...
Ah I didn't see your video on the shared link above. If there's such a bug in tailwind v4 integration on qwik, perhaps you should consider to keep using v3 for the time being. Also, adding lint:false to your config should be very easy to do.
brisk agate
@silk zephyr I added it. But the difference was not visible to me. Perhaps I should use some performance and timing metrics to measure the difference.
silk zephyr
you can use vite-plugin-inspect
brisk agate
What does it do? I looked at it but could not find how it's useful for this case.