fix(deps): update dependency eslint-plugin-vue to ^10.5.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-vue (source)	^10.2.0 -> ^10.5.1

---

Release Notes

vuejs/eslint-plugin-vue (eslint-plugin-vue)

v10.5.1

Compare Source

Patch Changes

• Fixed vue/no-negated-v-if-condition rule to swap entire elements (#​2941)

v10.5.0

Compare Source

Minor Changes

• Added ignoredObjectNames option to vue/no-async-in-computed-properties (#​2927)
• Added ignorePattern option to vue/no-v-html (#​2857)
• Added sortLineLength option to vue/attributes-order (#​2759)
• Changed vue/component-name-in-template-casing globals option to support regex patterns (#​2928)
• Changed vue/valid-define-options to allow local literal constant references (#​2920)
• Changed vue/no-mutating-props and vue/no-side-effects-in-computed-properties rules to detect Object.assign mutations (#​2929)
• Added @stylistic/eslint-plugin as optional peer dependency (#​2884)

Patch Changes

• Changed vue/define-macros-order to ignore enum declarations and declare statements (#​2918)

v10.4.0

Compare Source

Minor Changes

• Added ignoreParents option to vue/no-deprecated-slot-attribute (#​2784)
• Added new vue/no-negated-v-if-condition rule (#​2794)
• Added new vue/no-negated-condition rule (#​2795)

Patch Changes

• Resolved TypeScript compatibility issues introduced by eslint-typegen (#​2790)
• Fixed inconsistent quotes in vue/block-lang error messages (#​2805)

v10.3.0

Compare Source

Minor Changes

• Added @typescript-eslint/parser as an optional peer dependency (#​2775)
• Add TypeScript IntelliSense support via eslint-typegen (#​2770)
• vue/no-deprecated-slot-attribute ignore option now supports regex patterns (#​2773)

Patch Changes

• Fixed false negatives when using typescript-eslint v8 in vue/script-indent rule (#​2775)
• Update resources (#​2752)
• vue/no-restricted-html-elements now also checks SVG and MathML elements (#​2755)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nuxt/​test-utils@​3.19.2 ⏵ 3.20.1	+1		+1	+8
	eslint-plugin-vue@​10.2.0 ⏵ 10.5.1			+1	-2
	@​nuxt/​module-builder@​1.0.1 ⏵ 1.0.2	+1			+4
	nuxt@​4.2.1
	@​nuxt/​devtools@​3.1.0

View full report

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/poupe-ui/eslint-config/@poupe/eslint-config@156

commit: 5fff98f

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] → npm/@nuxt/[email protected] → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report