Update dependency vue-tsc to v3.1.1

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vue-tsc (source)	3.0.6 -> 3.1.1

---

Release Notes

vuejs/language-tools (vue-tsc)

v3.1.1

Compare Source

Features

• feat(language-server): support --tsdk command line arg (#​5691)

Bug Fixes

• fix(language-core): tolerate non-literal export default (#​5675) - Thanks to @​KazariEX!
• fix(language-core): use component instance props as fallthrough attributes (#​5686) - Thanks to @​KazariEX!
• fix(typescript-plugin): determine if variable is Ref by RefSymbol property (#​5687) - Thanks to @​KazariEX!
• fix(language-core): exclude effect of comments on root node (#​5689) - Thanks to @​KazariEX!
• fix(typescript-plugin): place __vue__ in project instead of program (#​5690)
• fix(component-type-helpers): remove deprecated $scopedSlots support for Vue 2
• fix(language-core): replace markdown links after sfc blocks processing (#​5695) - Thanks to @​KazariEX!
• fix(language-core): do not report unused error on __VLS_export (#​5696) - Thanks to @​KazariEX!

Other Changes

• refactor(language-core): reimplement writeGlobalTypes without side effects

v3.1.0

Compare Source

Performance

• perf(language-core): drop internal component (#​5532) - Thanks to @​KazariEX!

Other Changes

• refactor: drop Vue 2 support (#​5636) - Thanks to @​KazariEX!
• chore(lint): enforce use of type-only imports (#​5658) - Thanks to @​so1ve!
• ci: upgrade node version (#​5668) - Thanks to @​so1ve!
• refactor(typescript-plugin): move reactivity analysis logic to a seperate typescript plugin (#​5672) - Thanks to @​KazariEX!

v3.0.9

Compare Source

Features

• feat(language-server): support --tsdk command line arg (#​5691)

v3.0.8

Compare Source

Features

• feat(vscode): introduce vue.server.path setting (#​5647)

Bug Fixes

• fix(language-core): initialize properties of VueVirtualCode in constructor (#​5635) - Thanks to @​KazariEX!
• fix(vscode): flatten reactivity visualization decorators (#​5642) - Thanks to @​KazariEX!
• fix(vscode): normalize reactivity visualization ranges
• fix(vscode): patch typescriptServerPlugin languages without FS hack
• fix(language-service): do not provide semantic tokens and document highlights for non-file scheme files (#​5653) - Thanks to @​KazariEX!

Performance

• perf(typescript-plugin): redo single-file language service for reactivity visualization (#​5652)

Other Changes

• refactor(typescript-plugin): externalize reactivity analysis logic (#​5645) - Thanks to @​KazariEX!

v3.0.7

Compare Source

Bug Fixes

• fix(vscode): show welcome page only when opening a Vue file
• fix(language-core): generate slot parameters in the same way as interpolation (#​5618) - Thanks to @​KazariEX!
• fix(language-core): do not generate variables for builtin directives - Thanks to @​KazariEX!

Other Changes

• docs(vscode): add descriptions for premium feature configurations (#​5612) - Thanks to @​KazariEX!
• refactor(typescript-plugin): explicitly request parameters (#​5623)
• chore(lint): enable @typescript-eslint/no-unnecessary-condition (#​5630)
• refactor(language-server): reimplement Reactivity Visualization in typescript plugin (#​5632)
• refactor(language-server): parsing interpolations in extension client (#​5633)
• refactor(vscode): reimplement Focus Mode base on folding ranges (#​5634)
• chore(vscode): disable Focus Mode by default (#​5578)
• refactor(vscode): set delay of reactivity visualization updates to 250ms - Thanks to @​KazariEX!

---

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.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​grunt-jscs@​3.0.1
	npm/​grunt-postcss@​0.9.0
	npm/​karma-detect-browsers@​2.3.3
	npm/​grunt@​1.6.1
	npm/​grunt-exec@​3.0.0
	npm/​karma-firefox-launcher@​2.1.3
	npm/​karma-qunit@​4.2.1
	npm/​karma-chrome-launcher@​3.2.0
	npm/​grunt-contrib-cssmin@​5.0.0
	npm/​ip@​2.0.1
	npm/​karma@​6.4.4
	npm/​grunt-html@​17.0.1
	npm/​grunt-contrib-copy@​1.0.0
	npm/​grunt-contrib-concat@​2.1.0
	npm/​grunt-contrib-clean@​2.0.1
	npm/​grunt-contrib-less@​3.0.0
	npm/​grunt-contrib-jshint@​3.2.0
	npm/​grunt-contrib-uglify@​5.2.2
	npm/​karma-browserstack-launcher@​1.6.0
	npm/​grunt-stylelint@​0.10.1
	npm/​cross-env@​7.0.3

View full report

[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		npm/lodash@3.10.1 has a Critical CVE. CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12 From: xwiki-platform-core/xwiki-platform-bootstrap/src/main/package-lock.json → npm/grunt-jscs@3.0.1 → npm/lodash@3.10.1 ℹ Read more on: This package | This alert | What is a critical CVE? 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 support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lodash@3.10.1. 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.
Warn		npm/lodash@4.6.1 has a Critical CVE. CVE: GHSA-jf85-cpcp-j695 Prototype Pollution in lodash (CRITICAL) Affected versions: < 4.17.12 Patched version: 4.17.12 From: xwiki-platform-core/xwiki-platform-bootstrap/src/main/package-lock.json → npm/grunt-jscs@3.0.1 → npm/lodash@4.6.1 ℹ Read more on: This package | This alert | What is a critical CVE? 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 support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lodash@4.6.1. 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