diff --git a/src/docs/guide/usage/linter/rules/typescript/unbound-method.md b/src/docs/guide/usage/linter/rules/typescript/unbound-method.md
index 42b55ce6a56..30cb1ca91b8 100644
--- a/src/docs/guide/usage/linter/rules/typescript/unbound-method.md
+++ b/src/docs/guide/usage/linter/rules/typescript/unbound-method.md
@@ -11,6 +11,9 @@ const source = `https://github.com/oxc-project/oxc/blob/${ data }/crates/oxc_lin
diff --git a/src/docs/guide/usage/linter/rules/typescript/use-unknown-in-catch-callback-variable.md b/src/docs/guide/usage/linter/rules/typescript/use-unknown-in-catch-callback-variable.md
index f303cf44d30..d624700c375 100644
--- a/src/docs/guide/usage/linter/rules/typescript/use-unknown-in-catch-callback-variable.md
+++ b/src/docs/guide/usage/linter/rules/typescript/use-unknown-in-catch-callback-variable.md
@@ -8,6 +8,9 @@ const source = `https://github.com/oxc-project/oxc/blob/${ data }/crates/oxc_lin
# typescript/use-unknown-in-catch-callback-variable
+
+π This rule requires type information.
+
π§ An auto-fix is still under development.
diff --git a/src/docs/guide/usage/linter/rules/unicorn/no-array-reverse.md b/src/docs/guide/usage/linter/rules/unicorn/no-array-reverse.md
new file mode 100644
index 00000000000..81da782480e
--- /dev/null
+++ b/src/docs/guide/usage/linter/rules/unicorn/no-array-reverse.md
@@ -0,0 +1,76 @@
+
+
+
+
+# unicorn/no-array-reverse
+
+
+
+### What it does
+
+Prefer using `Array#toReversed()` over `Array#reverse()`.
+
+### Why is this bad?
+
+`Array#reverse()` modifies the original array in place, which can lead to unintended side effectsβespecially
+when the original array is used elsewhere in the code.
+
+### Examples
+
+Examples of **incorrect** code for this rule:
+
+```js
+const reversed = [...array].reverse();
+```
+
+Examples of **correct** code for this rule:
+
+```js
+const reversed = [...array].toReversed();
+```
+
+### Options
+
+#### allowExpressionStatement
+
+`{ type: boolean, default: true }`
+
+This rule allow `array.reverse()` as an expression statement by default,
+Pass allowExpressionStatement: false to forbid `Array#reverse()` even it's an expression statement.
+
+Examples of **incorrect** code for this rule with the `{ "allowExpressionStatement": false }` option:
+
+```js
+array.reverse();
+```
+
+## How to use
+
+To **enable** this rule in the CLI or using the config file, you can use:
+
+::: code-group
+
+```bash [CLI]
+oxlint --deny unicorn/no-array-reverse
+```
+
+```json [Config (.oxlintrc.json)]
+{
+ "rules": {
+ "unicorn/no-array-reverse": "error"
+ }
+}
+```
+
+:::
+
+## References
+
+-
Rule Source
diff --git a/src/docs/guide/usage/linter/rules/version.data.js b/src/docs/guide/usage/linter/rules/version.data.js
index 03bcb9bdbf7..5f3fa91285f 100644
--- a/src/docs/guide/usage/linter/rules/version.data.js
+++ b/src/docs/guide/usage/linter/rules/version.data.js
@@ -1,5 +1,5 @@
export default {
load() {
- return "7fc4aef229419ae73e4feae806eb73b7fed3b983";
+ return "b20b56df4f00f5f03bc3bd3977725c52d43bbb91";
},
};
diff --git a/src/docs/guide/usage/linter/rules/vue/define-emits-declaration.md b/src/docs/guide/usage/linter/rules/vue/define-emits-declaration.md
new file mode 100644
index 00000000000..8a774ba1fe0
--- /dev/null
+++ b/src/docs/guide/usage/linter/rules/vue/define-emits-declaration.md
@@ -0,0 +1,121 @@
+
+
+
+
+# vue/define-emits-declaration
+
+
+
+### What it does
+
+This rule enforces `defineEmits` typing style which you should use `type-based`, strict `type-literal` (introduced in Vue 3.3), or `runtime` declaration.
+This rule only works in setup script and `lang="ts"`.
+
+### Examples
+
+Examples of **incorrect** code for this rule:
+
+```vue
+// "vue/define-emits-declaration": ["error", "type-based"]
+
+
+// "vue/define-emits-declaration": ["error", "type-literal"]
+
+
+// "vue/define-emits-declaration": ["error", "runtime"]
+
+```
+
+Examples of **correct** code for this rule:
+
+```vue
+// "vue/define-emits-declaration": ["error", "type-based"]
+
+
+// "vue/define-emits-declaration": ["error", "type-literal"]
+
+
+// "vue/define-emits-declaration": ["error", "runtime"]
+
+```
+
+### Options
+
+```
+"vue/define-emits-declaration": ["error", "type-based" | "type-literal" | "runtime"]
+```
+
+- `type-based` (default): Enforce type-based declaration
+- `type-literal`: Enforce type-literal declaration
+- `runtime`: Enforce runtime declaration
+
+## How to use
+
+To **enable** this rule in the CLI or using the config file, you can use:
+
+::: code-group
+
+```bash [CLI]
+oxlint --deny vue/define-emits-declaration --vue-plugin
+```
+
+```json [Config (.oxlintrc.json)]
+{
+ "plugins": ["vue"],
+ "rules": {
+ "vue/define-emits-declaration": "error"
+ }
+}
+```
+
+:::
+
+## References
+
+-
Rule Source
diff --git a/src/docs/guide/usage/linter/rules/vue/define-props-declaration.md b/src/docs/guide/usage/linter/rules/vue/define-props-declaration.md
new file mode 100644
index 00000000000..2127056d1df
--- /dev/null
+++ b/src/docs/guide/usage/linter/rules/vue/define-props-declaration.md
@@ -0,0 +1,88 @@
+
+
+
+
+# vue/define-props-declaration
+
+
+
+
+### What it does
+
+This rule enforces `defineProps` typing style which you should use `type-based` or `runtime` declaration.
+This rule only works in setup script and `lang="ts"`.
+
+### Examples
+
+Examples of **incorrect** code for this rule:
+
+```vue
+// "vue/define-props-declaration": ["error", "type-based"]
+
+
+// "vue/define-props-declaration": ["error", "runtime"]
+
+```
+
+Examples of **correct** code for this rule:
+
+```vue
+// "vue/define-props-declaration": ["error", "type-based"]
+
+
+// "vue/define-props-declaration": ["error", "runtime"]
+
+```
+
+### Options
+
+```
+"vue/define-props-declaration": ["error", "type-based" | "runtime"]
+```
+
+- `type-based` (default) enforces type-based declaration
+- `runtime` enforces runtime declaration
+
+## How to use
+
+To **enable** this rule in the CLI or using the config file, you can use:
+
+::: code-group
+
+```bash [CLI]
+oxlint --deny vue/define-props-declaration --vue-plugin
+```
+
+```json [Config (.oxlintrc.json)]
+{
+ "plugins": ["vue"],
+ "rules": {
+ "vue/define-props-declaration": "error"
+ }
+}
+```
+
+:::
+
+## References
+
+-
Rule Source
diff --git a/src/docs/guide/usage/linter/rules/vue/no-multiple-slot-args.md b/src/docs/guide/usage/linter/rules/vue/no-multiple-slot-args.md
new file mode 100644
index 00000000000..95268e4acd0
--- /dev/null
+++ b/src/docs/guide/usage/linter/rules/vue/no-multiple-slot-args.md
@@ -0,0 +1,80 @@
+
+
+
+
+# vue/no-multiple-slot-args
+
+
+
+### What it does
+
+Disallow passing multiple arguments to scoped slots.
+
+### Why is this bad?
+
+Users have to use the arguments in fixed order and cannot omit the ones they don't need.
+e.g. if you have a slot that passes in 5 arguments but the user actually only need the last 2 of them,
+they will have to declare all 5 just to use the last 2.
+
+More information can be found in [vuejs/vue#9468](https://github.com/vuejs/vue/issues/9468#issuecomment-462210146)
+
+### Examples
+
+Examples of **incorrect** code for this rule:
+
+```vue
+
+```
+
+Examples of **correct** code for this rule:
+
+```vue
+
+```
+
+## How to use
+
+To **enable** this rule in the CLI or using the config file, you can use:
+
+::: code-group
+
+```bash [CLI]
+oxlint --deny vue/no-multiple-slot-args --vue-plugin
+```
+
+```json [Config (.oxlintrc.json)]
+{
+ "plugins": ["vue"],
+ "rules": {
+ "vue/no-multiple-slot-args": "error"
+ }
+}
+```
+
+:::
+
+## References
+
+-
Rule Source
diff --git a/src/docs/guide/usage/linter/rules/vue/valid-define-props.md b/src/docs/guide/usage/linter/rules/vue/valid-define-props.md
new file mode 100644
index 00000000000..8c126f3c865
--- /dev/null
+++ b/src/docs/guide/usage/linter/rules/vue/valid-define-props.md
@@ -0,0 +1,122 @@
+
+
+
+
+# vue/valid-define-props
+
+
+
+### What it does
+
+This rule checks whether `defineProps` compiler macro is valid.
+
+This rule reports `defineProps` compiler macros in the following cases:
+
+- `defineProps` is referencing locally declared variables.
+- `defineProps` has both a literal type and an argument. e.g. `defineProps<{ /*props*/ }>({ /*props*/ })`
+- `defineProps` has been called multiple times.
+- Props are defined in both `defineProps` and `export default {}`.
+- Props are not defined in either `defineProps` or `export default {}`.
+
+### Why is this bad?
+
+Misusing `defineProps` can lead to runtime errors, and lost type safety.
+Vue may still compile the code, but properties may break silently or be typed incorrectly.
+
+### Examples
+
+Examples of **incorrect** code for this rule:
+
+```vue
+
+```
+
+```vue
+
+```
+
+```vue
+
+```
+
+```vue
+
+
+```
+
+Examples of **correct** code for this rule:
+
+```vue
+
+```
+
+```vue
+
+```
+
+```vue
+
+```
+
+```vue
+
+
+```
+
+## How to use
+
+To **enable** this rule in the CLI or using the config file, you can use:
+
+::: code-group
+
+```bash [CLI]
+oxlint --deny vue/valid-define-props --vue-plugin
+```
+
+```json [Config (.oxlintrc.json)]
+{
+ "plugins": ["vue"],
+ "rules": {
+ "vue/valid-define-props": "error"
+ }
+}
+```
+
+:::
+
+## References
+
+-
Rule Source