Tim MacDonald
Tim MacDonald
@patak-dev @bluwy I've just pushed some new commits to this based on the concerns you have (and @bluwy the testing you did 🤦♂️ my bad, sorry). This new approach only...
Thank you @patak-dev and @bluwy for your help with this one and thanks to the rest of the Vite team for taking the time to consider the PR.
Hey folks, I've hit this with the Laravel integration as well, and I've proposed the following fix: https://github.com/vitejs/vite/pull/9928 It is my opinion that if two files are the same e.g....
@nunomaduro loving where this is headed.
@ralphjsmit changing the throwing logic would make it inconsistent with the Http client. I think it might be nice if it was consistent and perhaps had additional affodances to handle...
You may create an application middleware that turns it back on or off for only the routes you would like. For example, in Laravel we may do the following... ```php...
FYI: In the Laravel Jetstream, we solve this by not externalising the server. ```js import { defineConfig } from 'vite'; import laravel from 'laravel-vite-plugin'; import vue from '@vitejs/plugin-vue'; export default...
Gonna close this one and track in the PR. Thanks!
I would rather we didn't merge this as it currently is, as I can happily run Vite in Sail without any extra work. ``` composer create-project laravel/laravel sail-test cd sail-test...
@mike-healy I'm on Mac. WSL2 is a known issue that we are working on improving, which is the intention of this PR: https://github.com/laravel/vite-plugin/pull/42 , which is yet to be tagged.