HMR vite flow #3

JoshuaCrewe commented 2026年03月02日 11:02:00 +01:00

At the moment the build is using vite build --watch which is my preference overall. I don't want a development server required which needs the port being kept a track of. This is however how vite wants to work so it would be good to have this working

To get it working we are looking at :

• Updating package.json to use vite watch
• Figuring out what the path on the dev server the assets are served at (this seems basically impossible)
• Create a PHP function to detect this mode and load via the above figured out URL
• Mode detection is best by looking for the hot file (make sure this is output to somewhere)
• Update index-asset-php plugin to work on both modes (closeBundle vs buildStart)

At the moment the build is using `vite build --watch` which is my preference overall. I don't want a development server required which needs the port being kept a track of. This is however how vite wants to work so it would be good to have this working To get it working we are looking at : - [ ] Updating package.json to use vite watch - [ ] Figuring out what the path on the dev server the assets are served at (this seems basically impossible) - [ ] Create a PHP function to detect this mode and load via the above figured out URL - [ ] Mode detection is best by looking for the hot file (make sure this is output to somewhere) - [ ] Update index-asset-php plugin to work on both modes (`closeBundle` vs `buildStart`)