just-vibeVite · inspect by default
/vite-config
Audit aliases, plugins, build options, and environment handling
Use to inspect effective configuration; vite-hmr or vite-assets handles a known failure surface.
Make it your own.
In Claude Code, use the slash command and add your context. In Codex, select vite-config from the just-vibe skill picker, then send the same brief.
Version 0.11.0 also supports /jv vite-config, /just-vibe vite-config and /jv:vite-config in Claude. See shortcut setup and context examples.
/just-vibe:vite-config Audit aliases and plugin order for the installed Vite version./just-vibe:vite-config Diagnose an alias that typechecks but fails in the production bundle./just-vibe:vite-config Inspect config source with no build permission; do not execute arbitrary imports.What the agent does
- Resolve command, mode, root, envDir, aliases and plugin order from the actual invoked script, and check version compatibility.
- Trace conflicting options, compare development with production behavior and TypeScript with bundler resolution, and propose focused corrections.
Inputs
- configuration files, intended behavior, and observed issue.
Optional context: scope, references, constraints, successCriteria, environment, mode, budget.
Scope
- Reads
- Aliases, plugins/order, build targets, server options, and environment handling.
- Writes
- Inspect/plan: inspect or propose; save requested artifacts only. Apply: edit the requested local implementation and perform relevant bounded checks while preserving unrelated work. Live data changes, remote actions and paid jobs require their resolved target and existing session authorization.
- Mode
- Inspect; configuration files, intended behavior, and observed issue. Apply for a requested configuration fix.
- Prerequisites
- Project manifests, lockfile, Vite/framework/plugin versions, and existing build scripts. Verify current version-specific documentation when changing configuration. Requested isolated verification may generate disposable build/cache artifacts; inspect their scripts first and preserve product files.
Expected output
- Effective configuration by invocation, unsupported or conflicting settings with reasoning and, in apply mode, a focused patch.
How the work is checked
- A TypeScript-only alias missing at runtime is identified; a version-unsupported option is not recommended.
When to stop or clarify
- Do not execute arbitrary config code during read-only inspection without considering its side effects. Missing build evidence remains unknown.
Handling missing context
- Infer
- Read manifests, lockfile, installed Vite/plugins, entry points, aliases, modes and current build scripts.
- Assume
- Preserve existing tooling and base-path conventions; in apply mode, make a local focused change when the brief identifies the behavior, and otherwise propose it.
- Ask
- Ask if the intended serving subpath or deployment target cannot be inferred and would change generated URLs; do not ask for versions present in the lockfile.
Technical guidance
- Evidence
- Read effective command/mode, root/envDir, aliases, plugins, define replacements and server restrictions.
- Method
- Trace each disputed option to its consuming tool; reconcile TypeScript paths with actual bundler resolution.
- Pitfall
- A config file can execute arbitrary imports; read-only inspection should not evaluate it just to discover values.
- Check
- Check the relevant dev and production resolution paths, including case-sensitive filenames and browser-exposed replacements.
Situational decisions
When a config function branches on command or mode: Assess each relevant branch statically before executing potentially side-effecting configuration.
The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.