chore(deps): update dependency vue-tsc to v1.8.27 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vue-tsc (source)	1.8.8 -> 1.8.27

---

Release Notes

vuejs/language-tools (vue-tsc)

v1.8.27

Compare Source

• fix(language-core): remove misuse of JSX.Element for compatible with vue 3.4 (https://github.com/vuejs/core/issues/9923)

v1.8.26

Compare Source

• fix: upgrade typescript-auto-import-cache to v0.3.1 to be compatible with TS 5.3 (https://github.com/volarjs/typescript-auto-import-cache/pull/3) (#​3802)

v1.8.25

Compare Source

• fix(component-type-helpers): correct type inference for FunctionalComponent (#​3766) - thanks @​pinguet62
• fix(language-core): camelize props for dynamic component (#​3774) - thanks @​so1ve

v1.8.24

Compare Source

• refactor(component-type-helpers): vue 2 types now move to vue-component-type-helpers/vue2 (#​3404)
• feat(language-core): expose defineEmits's arg and typeArg in parseScriptSetupRanges (#​3710) - thanks @​so1ve
• fix(language-core): strictTemplates fails to report unknown components (#​3539)
• fix(language-core): script syntax breaks if script options does not have trailing comma (#​3755)
• fix(language-core): script syntax breaks if options are enclosed in parentheses (#​3756)
• fix(language-core): allow using as with multiple <script> blocks (#​3733) - thanks @​so1ve
• fix(language-core): component type narrowing not working in template
• fix(language-core): incremental insertion incorrect if input <script setup> tag above <script> tag (#​3743) - thanks @​so1ve
• fix(language-core): don't camelize attributes for plain elements (#​3750) - thanks @​rchl
• fix(vscode): syntax highlighting for .prop shorthand (#​3729) - thanks @​so1ve

Volar.js 1.11.1 updates:

• fix: browser integration no longer requires node polyfill (https://github.com/volarjs/volar.js/pull/70)
• fix: document continuous change merge results are incorrect in WebStorm (https://github.com/volarjs/volar.js/pull/77) - thanks @​browsnet

v1.8.22

Compare Source

• fix: experimentalResolveStyleCssClasses: "always" not working (#​3689) - thanks @​maIIady
• fix: __VLS_Prettify missing for dts build when uses withDefaults() (#​3691)

v1.8.21

Compare Source

Volar.js 1.10.5 updates:

• fix(monaco): completion cannot insert text starting with $ (https://github.com/volarjs/volar.js/issues/69)
• fix(typescript): automatic type acquisition not working since v1.10.0

v1.8.20

Compare Source

• feat: added Italian integration documentation
• feat: enforce v-bind argument to be an object (#​3666) - thanks @​so1ve
• fix: JSDoc comments not emitted when using type-only defineProps macro (#​3645)
• fix: autocomplete for directive comments without a space (#​3665) - thanks @​so1ve
• fix: fix slot type when using a interpolation in template string (#​3657) - thanks @​so1ve
• fix: add autocomplete for v-slot parameters (#​3661) - thanks @​so1ve
• fix: export correct SlotsPropertyName for vue2 (#​3669) - thanks @​zhiyuanzmj
• fix(types): infer discriminated unions in child component props (#​3672) - thanks @​davidmatter
• fix: access to slots directly (#​3671) - thanks @​so1ve
• fix: autocomplete not working for $event (#​3668) - thanks @​so1ve
• perf: remove duplicate virtual code for native tags
• chore: rename volar to vue in diagnostics (#​3667) - thanks @​so1ve
• chore: publish ts plugin to open-vsx (#​3589) - thanks @​brc-dd

Full-time Support by

WebContainer API is here.

Our Platinum Sponsors

	The Intuitive Web Framework
	The Progressive JavaScript Framework

Our Silver Sponsors

Add you via GitHub Sponsors or Open Collective

v1.8.19

Compare Source

• feat: no longer checking save time (#​3650)
• fix(ts-plugin): tsserver doesnt have updated list of external files when new vue files are added (required TS 5.3) (#​3555) (#​3649)
• fix: false positive error when accessing local variables in defineProps parameter (#​3643) (#​3644) - thanks @​so1ve

v1.8.18

Compare Source

Upgrade required VSCode version to 1.82.0 (#​3642)

v1.8.17

Compare Source

• fix: extension cannot run on vscode versions lower than 1.82.0 (#​3631) (#​3635)
• fix: make defineProps work when reading a property from defineProps() (#​3633) - thanks @​so1ve
• fix: avoid reading props from __VLS_ctx (#​3636) - thanks @​so1ve
• fix: regression with defineExpose (#​3639) - thanks @​so1ve

v1.8.16

Compare Source

• fix: merge default export's properties properly (#​3600) - thanks @​so1ve
• fix: accurate exposed type with refs in generic component (#​3604) - thanks @​so1ve
• fix: make emits type correct when user assigns emit function a custom name (#​3624) - thanks @​so1ve

Volar.js 1.10.3 updates:

• fix: performance issue with o(n^2) complexity of directoryExists() (https://github.com/volarjs/volar.js/issues/66) - thanks @​Akryum
• fix: directory named "constructor" could crash (https://github.com/volarjs/volar.js/issues/65) - thanks @​Dmitrigar, @​franz-bendezu

v1.8.15

Compare Source

• fix: props type missing in JS component context (#​3592)
• fix: ignore $emit return type for Vue 2 (#​3596)

v1.8.14

Compare Source

• feat: defineEmit now able to infer event types with more than 4 overloads (#​3379) (#​1855)
• feat: more accurately distinguish component internal context and external context types (#​3591) (#​3517) - thanks @​so1ve
• fix: don't import alias macros (#​3576) - thanks @​sxzz
• fix: make generic components' emit type compactible with Vue core types (#​3569) (#​3257) - thanks @​so1ve
• fix: use universal __VLS_ConstructorOverloads when emits type is not inlined (#​3585) - thanks @​so1ve
• fix: inherit emits props and supports generic component emit type for JSX (#​3533) (#​3289) (#​3476) - thanks @​so1ve
• perf: generate less TS virtual code for TS performance (#​3581)

v1.8.13

Compare Source

• fix: generate valid syntax when noPropertyAccessFromIndexSignature is not enabled (#​3575) - thanks @​so1ve

v1.8.12

Compare Source

• feat: support vitepress's code snippet import (#​3559) - thanks @​so1ve
• fix(component-meta): fix modules interoperability with vue-component-type-helper
• fix: avoid losing generic types with strictTemplates: false (#​3565) - thanks @​so1ve
• fix: format slots with typeannotation correctly (#​3573) - thanks @​so1ve

v1.8.11

Compare Source

• feat: slot references codeLens counting fragment default slot (#​932)
• fix: correct message for @vue-expect-error (#​3541) - thanks @​so1ve
• fix: avoid global macros conflicts with local variables (#​3550) - thanks @​so1ve
• fix: script setup comments at top breaks global macros (#​3549) - thanks @​so1ve
• fix(vue-tsc): prevent rebuild in incremental mode throwing error (#​3556) - thanks @​blake-newman

v1.8.10

Compare Source

• feat: added Portuguese integration documentation (#​3535)
• feat: exposed configFileName for createParsedCommandLineByJson() function (#​3456) - thanks @​qmhc
• feat: support nested plugins (#​3530) - thanks @​so1ve
• feat(vscode): add vue.server.runtime setting and support for Bun runtime
• feat(vscode): add vue.server.path setting for customize server module path
• fix: correctly hyphen-case props (#​3424) - thanks @​so1ve
• fix: generic components should respect strictTemplates (#​3487) - thanks @​so1ve
• fix(vue-component-type-helpers): correctly handle generic components when using ComponentExposed (#​3536) - thanks @​so1ve

---

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 has been generated by Mend Renovate. View repository job log here.

[github-actions]

❌ @renovate[bot] the signed-off-by was not found in the following 1 commits:

• 6fe9601: chore(deps): update dependency vue-tsc to v1.8.27

📝 What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

❔ Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

[github-actions]

❌ @renovate[bot] the signed-off-by was not found in the following 1 commits:

• 2c07cdc: chore(deps): update dependency vue-tsc to v1.8.27

📝 What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

❔ Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'

[github-actions]

❌ @renovate[bot] the signed-off-by was not found in the following 1 commits:

• 2c07cdc: chore(deps): update dependency vue-tsc to v1.8.27

📝 What should I do to fix it?

All proposed commits should include a sign-off in their messages, ideally at the end.

❔ Why it is required

The Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

Contributors sign-off that they adhere to these requirements by adding a Signed-off-by line to commit messages.

This is my commit message

Signed-off-by: Random Developer <randomdeveloper@example.com>

Git even has a -s command line option to append this automatically to your commit message:

$ git commit -s -m 'This is my commit message'