feat: merge oxlint config

Author: fengmk2

Cargo.lock

@@ -39,7 +39,7 @@ anyhow = "1.0.98"
 # Safe to migrate back to the official ast-grep release once PR #2359 is merged and a new version is published.
 ast-grep-config = { git = "https://github.com/fengmk2/ast-grep.git", rev = "2f4c6924438a72e136485f0e14cd136b2e17d8d3" }
 ast-grep-core = { git = "https://github.com/fengmk2/ast-grep.git", rev = "2f4c6924438a72e136485f0e14cd136b2e17d8d3" }
-ast-grep-language = { git = "https://github.com/fengmk2/ast-grep.git", rev = "2f4c6924438a72e136485f0e14cd136b2e17d8d3", default-features = false, features = ["lang-bash"] }
+ast-grep-language = { git = "https://github.com/fengmk2/ast-grep.git", rev = "2f4c6924438a72e136485f0e14cd136b2e17d8d3", default-features = false, features = ["lang-bash", "lang-typescript"] }
 backon = "1.3.0"
 bincode = "2.0.1"
 bstr = { version = "1.12.0", default-features = false, features = ["alloc", "std"] }

Cargo.toml

@@ -0,0 +1,115 @@
+# ast-grep rules for migrating .oxlintrc configuration to vite.config.ts
+#
+# These rules merge oxlint configuration from .oxlintrc into the defineConfig
+# call in vite.config.ts, following the vite-plus unified configuration approach.
+#
+# Usage:
+# The migration script should:
+# 1. Read .oxlintrc JSON content
+# 2. Convert it to TypeScript object literal format
+# 3. Replace __OXLINT_CONFIG__ placeholder with the actual config
+# 4. Run: sg scan -r oxlint-config.yaml vite.config.ts -U
+#
+# Example workflow:
+#
+#   # Step 1: Create rule file with actual oxlint config
+#   cat > /tmp/migrate-oxlint.yaml << 'EOF'
+#   ---
+#   id: merge-oxlint-config
+#   language: TypeScript
+#   rule:
+#     pattern: |
+#       defineConfig({
+#         $$$CONFIG
+#       })
+#   fix: |-
+#     defineConfig({
+#       $$$CONFIG
+#       lint: {
+#         rules: {
+#           'no-unused-vars': 'error',
+#           'no-console': 'warn',
+#         },
+#         ignorePatterns: ['dist', 'node_modules'],
+#       },
+#     })
+#   EOF
+#
+#   # Step 2: Run ast-grep
+#   sg scan -r /tmp/migrate-oxlint.yaml vite.config.ts -U
+#
+#   # Step 3: Remove old config file
+#   rm .oxlintrc
+#
+# For programmatic usage, use the vite_migration Rust crate which provides
+# proper JSON to TypeScript conversion.
+
+# Rule 1: Add lint config to defineConfig with existing properties
+# Matches:
+#   defineConfig({
+#     plugins: [...],
+#     server: {...},
+#   })
+# Result:
+#   defineConfig({
+#     plugins: [...],
+#     server: {...},
+#     lint: {...},
+#   })
+---
+id: add-lint-config-to-defineconfig
+language: TypeScript
+severity: info
+message: 'Add lint configuration to vite.config.ts'
+note: 'Migrating oxlint configuration from .oxlintrc to vite.config.ts'
+rule:
+  pattern: |
+    defineConfig({
+      $$$EXISTING_CONFIG
+    })
+fix: |-
+  defineConfig({
+    $$$EXISTING_CONFIG
+    // lint configuration (merged from .oxlintrc)
+    lint: __OXLINT_CONFIG__,
+  })
+files:
+  - '**/vite.config.ts'
+  - '**/vite.config.mts'
+  - '**/vite.config.js'
+  - '**/vite.config.mjs'
+ignores:
+  - '**/node_modules/**'
+  - '**/dist/**'
+
+# Rule 2: Detect defineConfig with function callback (warning only)
+# This pattern requires manual migration
+# Matches: defineConfig((env) => ({ ... }))
+---
+id: detect-function-defineconfig
+language: TypeScript
+severity: warning
+message: 'defineConfig uses a function callback - manual migration required'
+note: |
+  The defineConfig uses a function callback pattern which cannot be
+  automatically migrated. Please manually add the lint configuration:
+
+  export default defineConfig((env) => ({
+    ...existingConfig,
+    lint: {
+      rules: {
+        // your rules from .oxlintrc
+      },
+    },
+  }));
+rule:
+  # Using explicit arrow function pattern to match callback style
+  pattern: defineConfig(($PARAMS) => $BODY)
+files:
+  - '**/vite.config.ts'
+  - '**/vite.config.mts'
+  - '**/vite.config.js'
+  - '**/vite.config.mjs'
+ignores:
+  - '**/node_modules/**'
+  - '**/dist/**'

crates/vite_migration/rules/oxlint-config.yaml

@@ -0,0 +1,72 @@
+# Simple ast-grep rule for adding lint config to defineConfig
+#
+# This rule is designed to be used programmatically where the
+# __OXLINT_CONFIG__ placeholder is replaced with actual content.
+#
+# Usage:
+#   1. Read .oxlintrc content and convert to TypeScript
+#   2. Replace __OXLINT_CONFIG__ in this file with the converted content
+#   3. Run: sg scan -r oxlint-simple.yaml vite.config.ts -U
+#
+# Example:
+#   # Create a rule with actual config content
+#   cat > /tmp/oxlint-rule.yaml << 'EOF'
+#   ---
+#   id: merge-oxlint-to-vite-config
+#   language: TypeScript
+#   rule:
+#     pattern: |
+#       defineConfig({
+#         $$$CONFIG
+#       })
+#   fix: |-
+#     defineConfig({
+#       $$$CONFIG
+#       lint: {
+#         rules: {
+#           'no-console': 'warn',
+#         },
+#       },
+#     })
+#   EOF
+#   sg scan -r /tmp/oxlint-rule.yaml vite.config.ts -U
+#
+# Note: This rule handles the common case where defineConfig receives
+# an object literal directly. For function callbacks or complex patterns,
+# manual migration may be needed.
+
+---
+id: merge-oxlint-to-vite-config
+language: TypeScript
+severity: info
+message: 'Merge .oxlintrc configuration into vite.config.ts'
+note: |
+  This rule adds the lint configuration from .oxlintrc to the
+  defineConfig call in vite.config.ts.
+
+  Before: defineConfig({ plugins: [...] })
+  After:  defineConfig({ plugins: [...], lint: {...} })
+
+rule:
+  # Match defineConfig call with object argument
+  # Using multiline pattern to correctly capture the content
+  pattern: |
+    defineConfig({
+      $$$CONFIG
+    })
+
+fix: |-
+  defineConfig({
+    $$$CONFIG
+    // lint configuration (migrated from .oxlintrc)
+    lint: __OXLINT_CONFIG__,
+  })
+
+files:
+  - '**/vite.config.ts'
+  - '**/vite.config.mts'
+  - '**/vite.config.js'
+  - '**/vite.config.mjs'
+ignores:
+  - '**/node_modules/**'
+  - '**/dist/**'

crates/vite_migration/rules/oxlint-simple.yaml

@@ -1,3 +1,5 @@
 mod package;
+mod vite_config;
 
 pub use package::rewrite_scripts;
+pub use vite_config::{MergeResult, merge_json_config};