chore(deps): update all non-major dependencies (main) - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxt/devtools (source)	^1.2.0 -> ^1.3.1
@vue/language-core (source)	2.0.16 -> 2.0.17
execa	9.0.1 -> 9.0.2
rimraf	5.0.5 -> 5.0.6
vue-tsc (source)	2.0.16 -> 2.0.17

---

Release Notes

nuxt/devtools (@​nuxt/devtools)

v1.3.1

Compare Source

Bug Fixes

• module builder chunk path patch (87199a1)

v1.3.0

Compare Source

Bug Fixes

• devtools: optimize the home page layout (#​654) (a1ad266)
• upgrade vite-plugin-vue-inspector, fix #​657 (f67f0f2)

Features

• components tree panel (#​655) (3162269)
• hide devtools when printing (#​648) (1be7b2d)

vuejs/language-tools (@​vue/language-core)

v2.0.17

Compare Source

Features

• language-core: add JSDoc support for component (#​2377)
• language-core: add JSDoc support for script setup binding variables (#​3409)
• language-core: add class component support (#​4354)
• language-service: re-support scoped class links in template (#​4357)
• typescript-plugin: create script setup block when auto import if needed
• typescript-plugin: add JSDoc support for events in template (#​4365)
• component-meta: add JSDoc tags support for events
• language-core: support defineOptions (#​4362) - Thanks @​zhiyuanzmj

Bug Fixes

• language-core: hover not working for intrinsic element event name
• language-core: showing false declared but not used errors for functions used in v-on="{}" (#​4333)
• language-core: fix nameless event expression formatting
• language-core: types imported in the <script setup> should not be used as a variable in template (#​4353)
• language-core: renaming classname within scoped not working (#​4355)
• language-core: <style> completions and html custom data completions not provided in some cases (#​4092)
• language-core: improve code action edits mapping fault tolerance
• language-core: support defineModel for generic component (#​4345) - Thanks @​zhiyuanzmj
• language-service: completion cannot trigger in SFC root
• component-meta: forceUseTs options not working

Other Changes

• Upgrade Volar from v2.2.0 to v2.2.2.
  • fix(language-server): pass correct languageId when creating virtual code (https://github.com/volarjs/volar.js/issues/173)
  • fix(typescript): additional completion not working in plugin (#​4323)
• Upgrade Volar services from v0.0.42 to v0.0.44.
  • feat(typescript): code action edits respect editor formatting settings (https://github.com/volarjs/services/issues/30)
  • fix(typescript): not being able to jump to shims module definition
  • fix(typescript): allowTextChangesInNewFiles never true for embedded documents
  • perf(typescript): check command resolve capability only for specific refactors (https://github.com/volarjs/services/issues/94)
• The following extensions have been added to Hybrid Mode’s compatibility whitelist:
  • mxsdev.typescript-explorer
• Deprecated vueCompilerOptions.experimentalUseElementAccessInTemplate
• Specify packageManager (#​4358) - Thanks @​so1ve
• docs: emoved possibly redundant duplicate reference (#​4348) - Thanks @​artshade
• language-service: temporarily remove references codeLens (#​4364)

sindresorhus/execa (execa)

v9.0.2

Compare Source

isaacs/rimraf (rimraf)

v5.0.6

Compare Source

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	0 B
npm/[email protected]	None	0	51.5 kB	kael
npm/[email protected]	environment, filesystem, unsafe	0	8.39 MB	prettier-bot
npm/[email protected]	None	0	0 B
npm/[email protected]	None	0	32.4 MB	typescript-bot
npm/[email protected]	None	0	0 B

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

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 support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]