Use Claude to Set Up Your Vite Build Configuration
Vite's defaults work great until they don't. When you need path aliases, environment-specific builds, chunk splitting, or library mode, ask Claude to write the config rather than trawling through docs.
"Write a vite.config.ts for a Vue 3 + TypeScript project:
- Alias @ to ./src
- Proxy /api to http://localhost:8000 in dev only
- Split vendor chunks: vue ecosystem separate from UI library separate from utils
- Inline SVGs as Vue components via vite-svg-loader
- Source maps in production for Sentry error tracking
- Tree-shake lodash-es so only used methods are bundled"
Chunk splitting is the setting most people get wrong — one big vendor bundle means users re-download all unchanged libraries on every deploy. Claude sets up manualChunks with sensible groups and explains the trade-offs between granularity and HTTP request count.
build: {
rollupOptions: {
output: {
manualChunks: {
'vue-vendor': ['vue', 'vue-router', 'pinia'],
'ui-vendor': ['@headlessui/vue', '@heroicons/vue'],
}
}
}
}
For Laravel + Vite projects, mention you're using laravel-vite-plugin — it adjusts the manifest path, hot reload config, and asset helpers so everything works with Blade templates out of the box.
Vite config drift causes subtle build differences between environments — write it properly once with Claude and version control it.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.