Backend integration in development

Clear and concise description of the problem

if I want to use vite with my backend integration, I don’t know if vite client is running and I have to take :

<script type="module" src="http://localhost:3000/@vite/client"></script>
<script type="module" src="http://localhost:3000/main.js"></script>

or if I have to use files from manifest.json :

<link rel="stylesheet" href="/assets/{{ manifest['main.js'].css }}" />
<script type="module" src="/assets/{{ manifest['main.js'].file }}"></script>

As a developer, I think it would be interesting to know if files documented by manifest.json are out of date when I’m running the vite client : http://localhost:3000/@vite/client

Suggested solution

delete the manifest.json when I’m running the vite dev client. so I know that I have to call

<script type="module" src="http://localhost:3000/@vite/client"></script>
<script type="module" src="http://localhost:3000/main.js"></script>

Alternative

update the manifest.json with dev informations when I’m running the vite dev client.

[RentecTravis]

In my case I would love to use Vite to replace Webpack in our PHP app, for faster build times during development. Right now that’s not an option.

Most pages have their own entrypoints. We scan manifest files generated by Webpack in both development and production mode to render out all the <script> and <link> tags for the current page.

The Alternative option stated above - generating manifest.json when running vite in development mode - would be ideal. This would enable us to use Vite.

[lhapaipai]

hi @bluwy, my issue was : if you use vite with a backend like Symfony. you use the manifest.json to generate your entrypoints. if your manifest is present, you parse the file to determine the scripts to include. if your manifest is not present, you create a connection with the dev server. but if you run the dev server and your manifest is still present you have no easy way to know that you have to include in your script tag the connection to the dev server.

this issue is solved with https://github.com/lhapaipai/vite-plugin-symfony