Use Vite with the Laravel plugin and load the entry points through Blade: ```bash npm install ``` ```js // vite.config.js import laravel from 'laravel-vite-plugin'; import { defineConfig } from 'vite'; export default defineConfig({ plugins: [laravel(['resources/css/app.css', 'resources/js/app.js'])], }); ``` ```blade @vite(['resources/css/app.css', 'resources/js/app.js']) ``` Use `npm run dev` for HMR and `npm run build` for production. Vite handles asset versioning; do not add manual cache-b...
549 stars
0 votes
0 copies
1 view
Added September 5, 2026
developmentbash
Security analysis
A96/100
mediumInstalls packages at runtime which could introduce malicious dependencies
Installs into .claude/skills of the current project.
Are you the author of Laravel Tooling?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-laravel-tooling-0ed3e21e)
Use Vite with the Laravel plugin and load the entry points through Blade:
```bash
npm install
```
```js
// vite.config.js
import laravel from 'laravel-vite-plugin';
import { defineConfig } from 'vite';
export default defineConfig({
plugins: [laravel(['resources/css/app.css', 'resources/js/app.js'])],
});
```
```blade
@vite(['resources/css/app.css', 'resources/js/app.js'])
```
Use `npm run dev` for HMR and `npm run build` for production. Vite handles asset versioning; do not add manual cache-busting logic or keep Laravel Mix configuration in parallel.
