Claude Code often writes oxlint(/oxfmt) config to .oxlintrc.json(/.oxfmtrc.json) instead of vite.config.ts #1031

Activity

1. naitokosuke

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Mar 18, 2026
2. connorshea commented on Mar 22, 2026

   

   connorshea

   on Mar 22, 2026

   Contributor

   More actions

   Could potentially add optional Claude Hooks hooks to block Claude from creating the oxfmt/oxlint-specific files?
3. connorshea commented on Apr 5, 2026

   

   connorshea

   on Apr 5, 2026

   Last edited by connorshea

   Contributor

   More actions

   I put together hooks for this, plus for blocking some commands that vp should be handling (npm install, etc.) :)

   https://gist.github.com/connorshea/f2a19e955bcc54e50b33afc7e598bf97

   For the config file blocking specifically, you can add these to the repo.

   .claude/hooks/enforce-vp-config.sh in a repo:

   #!/bin/bash
   # .claude/hooks/enforce-vp-config.sh
   # Block creation/editing of standalone oxlint/oxfmt config files.
   # NOTE: Make sure to mark this script as executable with `chmod +x`.
   INPUT=$(cat)
   FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // empty')
   
   BASENAME=$(basename "$FILE_PATH" 2>/dev/null)
   
   case "$BASENAME" in
     .oxlintrc.json|.oxlintrc.jsonc|oxlint.config.ts|.oxfmtrc.json|.oxfmtrc.jsonc|oxfmt.config.ts)
       jq -n '{
         hookSpecificOutput: {
           hookEventName: "PreToolUse",
           permissionDecision: "deny",
           permissionDecisionReason: "Do not create standalone oxlint/oxfmt config files. Configure linting and formatting in `vite.config.ts` instead."
         }
       }'
       exit 0
       ;;
   esac
   
   exit 0

   And .claude/settings.json to trigger it on writes/edits:

   {
     "$schema": "https://json.schemastore.org/claude-code-settings.json",
     "hooks": {
       "PreToolUse": [
         {
           "matcher": "Write|Edit",
           "hooks": [
             {
               "type": "command",
               "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/enforce-vp-config.sh",
               "timeout": 2
             }
           ]
         }
       ]
     }
   }

   I think we could use the if syntax in settings.json to filter this down a bit more so it doesn't run unnecessarily as often, but it should be quite fast. It requires jq to be installed, but the Claude Code hooks docs use it a lot, so ¯_(ツ)_/¯

   👍React with 👍1Reacted by kii
4. naokihaba commented on May 12, 2026

   

   naokihaba

   on May 12, 2026

   Last edited by naokihaba

   Collaborator

   More actions

   As a future idea: Once the oxlint plugin (#1408) becomes available, it may be possible to automatically fix this misconfiguration, similar to the approach proposed for IDE configuration files in #1456.

   For example, a rule such as vite-plus/no-standalone-oxlint-config could detect standalone configuration files like .oxlintrc.json or oxfmt.config.ts. Then, using --fix, the configuration could be migrated into vite.config.ts and the original files deleted.

   In combination with improvements to CLAUDE.md, it would be possible to automatically correct instances where Claude Code accidentally creates these files by running vp check --fix.

   ❤️React with ❤️3Reacted by MK (fengmk2), sangwook and ナイトウコウスケ
5. Boshen

   added this to the Beta milestone on May 18, 2026
6. fengmk2

   closed this as a duplicateof Use oxlint plugin to validate and auto-fix IDE configuration issues #1456 on May 18, 2026