Why use Vite for development?

[GiorgioPortalVBR]

Hi!

I'm making this question out of ignorance and I'd love some insight into this.
I've started this project testing with a setup from Herd and that one seems to have reloading from the file.
Once I've started trying to dockerize the project it's using Vite for the server and this one seems to be a lot slower.
Any recommendations on making the setup run faster?

Many thanks,
Gonzako

[rw4lll]

Hi @GiorgioPortalVBR !

Could you share a bit more about your setup? Are you referring to the development environment example? What OS, architecture, and Docker installation are you using? (e.g., Mac/Arm, Mac/Intel, WSL, Docker Desktop). Also, are you using our test Laravel app or integrating it into your existing Laravel project?

[GiorgioPortalVBR]

Hi,
Yes I'm referring to the development side of the example. I'm testing on a windows machine using WSL/Docker Desktop. It's using a default development app provided by laravel and I've integrated your changes following this guide and translating the updated changes in this repositorty. Production I've gotten to work perfectly it's just development side that's giving me real issue. ATM, I'm just using a local ngix service to test changes on the website before pushing to the server.

[rw4lll]

Hi @GiorgioPortalVBR ,

Apologies for the delay in getting back to you – I appreciate your patience! Here are a couple of key points that might help with the issues you’re seeing in the development environment:

1. Xdebug in Development

Xdebug is enabled by default with full modes (develop, coverage, debug, profile), which can significantly slow things down, especially in Windows/WSL environments. If you’re not actively debugging, consider disabling it by setting XDEBUG_ENABLED=false in your .env file or Docker Compose. This should improve performance during development.

2. WSL Path Considerations
   Make sure your Laravel project files are stored within the WSL2 native filesystem (e.g., /home/username/project) instead of on a Windows-mounted path like /mnt/c/.... Windows paths can cause permission and sync issues when bind-mounted into Docker, so moving the project into WSL2’s native filesystem is a great way to avoid these problems.

I hope these suggestions help! Let me know how it goes. 🙌

[niyozbek]

Hi, Yes I'm referring to the development side of the example. I'm testing on a windows machine using WSL/Docker Desktop. It's using a default development app provided by laravel and I've integrated your changes following this guide and translating the updated changes in this repositorty. Production I've gotten to work perfectly it's just development side that's giving me real issue. ATM, I'm just using a local ngix service to test changes on the website before pushing to the server.

Hi @GiorgioPortalVBR , I have had some issues with WSL/Docker Desktop. Using WSL->ubuntu with Docker Desktop caused me lot's of troubles. These two had a conflict, but you may not see any obvious errors. Therefore, I removed Docker Desktop, which I think might be helpful in your case too.