Define CSS and JavaScript as Vite entry points and include them from the Blade layout: ```js // vite.config.js export default defineConfig({ plugins: [laravel(['resources/css/app.css', 'resources/js/app.js'])], }); ``` ```blade @vite(['resources/css/app.css', 'resources/js/app.js']) ``` Run `npm run dev` during development and `npm run build` for the production bundle. Keep asset code in `resources/`, use the Laravel plugin for integration, and avoid manual database or asset-manifest edits. V...
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-affd6964)
Define CSS and JavaScript as Vite entry points and include them from the Blade layout:
```js
// vite.config.js
export default defineConfig({
plugins: [laravel(['resources/css/app.css', 'resources/js/app.js'])],
});
```
```blade
@vite(['resources/css/app.css', 'resources/js/app.js'])
```
Run `npm run dev` during development and `npm run build` for the production bundle. Keep asset code in `resources/`, use the Laravel plugin for integration, and avoid manual database or asset-manifest edits. Verify the built application serves the generated assets and that Mix is not still being invoked.
