Update vue-tsc 3.2.7 → 3.3.1 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ vue-tsc (3.2.7 → 3.3.1) · Repo · Changelog

Release Notes

3.3.1

language-core

• fix: avoid extraneous children error for conditional slots (#6056) - Thanks to @KazariEX!

language-service

• refactor: replace scanner-based missing props hints detection with AST traversal - Thanks to @KazariEX!

typescript-plugin

• fix: get component prop details from symbols - Thanks to @KazariEX!
• fix: skip unchecked JS identifiers in component props (#6055) - Thanks to @KazariEX!

vscode

• fix: resolve typescript plugin path from resolved server path (#6058) - Thanks to @KazariEX!

Our Sponsors ❤️

This project is made possible thanks to our generous sponsors:

Special Sponsor
Next Generation Tooling
Platinum Sponsors
An approachable, performant and versatile framework for building web user interfaces.			Stay in the flow with instant dev experiences. No more hours stashing/pulling/installing locally — just click, and start coding.
Gold Sponsors
Silver Sponsors

Become a sponsor to support Vue tooling development

3.3.0

Features

Refined Autocomplete for Component Props

Previously, we inferred props used for autocomplete from the component itself's type, which did not work well with components whose props need to be inferred dynamically, such as generics or discriminated unions.

Now, we have improved this feature to better align with TS behavior. See the following example:

<script lang="ts" setup>
  defineProps<
    | { type: "foo"; foo: string }
    | { type: "bar"; bar: string }
  >();
</script>
<template>

<Self type="foo" :| />

<!--              ^ [foo, ...] -->

<Self type="bar" :| />

<!--              ^ [bar, ...] -->

</template>

When triggering completions at the two positions above, we will now get the props that are actually available in each corresponding case.

(PR: #5709)

Check Required Fallthrough Attributes

Consider the following structure:

<!-- basic.vue -->
<script lang="ts" setup>
  defineProps<{
    foo: string;
    bar: string;
  }>();
</script>

<!-- comp.vue -->
<script lang="ts" setup>
  import Basic from "./basic.vue";
</script>
<template>

<Basic />

</template>

When the fallthroughAttributes option is enabled on Comp, Comp inherits all props from Basic, allowing us to get prop completions for Basic when using Comp.

By default, however, the props inherited from Basic are all optional. This means we cannot enforce passing those required props when using Comp. At the same time, even if the required props from Basic are passed to Comp, Basic will still report missing prop errors.

After enabling the new checkRequiredFallthroughAttributes option on Comp, Comp will inherit Basic's props exactly as they are, and the missing prop errors on Basic inside Comp will disappear. This is because doing so is equivalent to promising that these required props should be passed when using Comp. Additionally, if some of the props required by Basic have already been passed directly to Basic, those props will be excluded from the inherited props.

(PR: #6049)

Bug Fixes

• In subprojects using project references, importing Vue files from another project will no longer trigger TS6307 errors (PR: #6048)
• When the js/ts.tsserver.experimental.enableProjectDiagnostics option is enabled, Vue files in large projects will no longer trigger diagnostics in an infinite loop (PR: #6051)

Changelog

Please refer to CHANGELOG.md for details.

❤️ Thanks to Our Sponsors

This project is made possible thanks to our generous sponsors:

Special Sponsor
Next Generation Tooling
Platinum Sponsors
An approachable, performant and versatile framework for building web user interfaces.			Stay in the flow with instant dev experiences. No more hours stashing/pulling/installing locally — just click, and start coding.
Gold Sponsors
Silver Sponsors

Become a sponsor to support Vue tooling development

3.2.9

language-core

• fix: do not process inline markdown syntax in semantic-aware segments (#6038) - Thanks to @KazariEX!
• perf: rewrite a subset of template node transforms (#5769) - Thanks to @KazariEX!

vscode

• fix: trigger file rename edits when moving folders with Vue files (#6046) - Thanks to @KazariEX!

workspace

• chore: bump volar services to 0.0.71 (#6043) - Thanks to @TRIS-H!

Our Sponsors ❤️

This project is made possible thanks to our generous sponsors:

Special Sponsor
Next Generation Tooling
Platinum Sponsors
An approachable, performant and versatile framework for building web user interfaces.			Stay in the flow with instant dev experiences. No more hours stashing/pulling/installing locally — just click, and start coding.
Gold Sponsors
Silver Sponsors

Become a sponsor to support Vue tooling development

3.2.8

language-core

• fix: replace inline code blocks after sfc blocks processing (#6024) - Thanks to @KazariEX!
• fix: support navigation for kebab-case declarations in GlobalComponents (#6026) - Thanks to @Gehbt!

language-service

• feat: support TS module resolution for SCSS @import navigation (#6033) - Thanks to @KazariEX!

typescript-plugin

• fix: replace language service per-method overrides with a proxy (#6035) - Thanks to @KazariEX!

vscode

• chore: upgrade reactive-vscode to v1.0.1 (#6019) - Thanks to @kermanx!

Our Sponsors ❤️

This project is made possible thanks to our generous sponsors:

Special Sponsor
Next Generation Tooling
Platinum Sponsors
An approachable, performant and versatile framework for building web user interfaces.			Stay in the flow with instant dev experiences. No more hours stashing/pulling/installing locally — just click, and start coding.
Gold Sponsors
Silver Sponsors

Become a sponsor to support Vue tooling development

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 46 commits:

• v3.3.1 (#6059)
• refactor(typescript-plugin): resolve import path preferences on tsserver side
• fix(vscode): resolve typescript plugin path from resolved server path (#6058)
• refactor(language-service): replace scanner-based missing props hints detection with AST traversal
• fix(language-core): avoid extraneous children error for conditional slots (#6056)
• fix(typescript-plugin): skip unchecked JS identifiers in component props (#6055)
• fix(typescript-plugin): get component prop details from symbols
• v3.3.0 (#6052)
• refactor(language-core): rename `Sfc` APIs to `IR`
• fix(typescript-plugin): unwrap nested type reference nodes
• docs: add `_vue:getComponentProps` to tsserver commands
• feat(language-core): check required fallthrough attributes (#6049)
• fix(vscode): avoid infinite diagnostics on Vue files when project diagnostics is enabled (#6051)
• fix(vscode): write typescript plugins at build time (#6050)
• refactor: avoid unnecessary language map iteration
• fix(language-service): reset to default data provider after running with vue data provider
• refactor(language-service): co-locate template data fetch and provide logic
• fix(language-service): strip `=""` only for plain boolean props completion edits
• fix(typescript-plugin): only return props when completion target is component node
• fix(language-service): avoid duplicate attrs and props requests
• refactor(language-core): rename template child flags to `treatTemplateAsFragment` for clarity
• fix(language-core): penetrate `v-if` branch fragments when collecting single root nodes
• fix(typescript-plugin): do not return fallback global completions as props
• fix(language-service): re-support `html.customData` (#5910)
• refactor: omit `.js` extension in import specifiers
• feat(typescript-plugin): refine props completion logic to follow TS behavior (#5709)
• fix(language-service): reuse ASTs for define assignment suggestion
• fix(vscode): include `extraFileExtensions` in tsserver `configure` request payload (#6048)
• v3.2.9 (#6045)
• fix(vscode): trigger file rename edits when moving folders with Vue files (#6046)
• chore: refine package publish file lists
• chore: pin `@typescript-eslint/eslint-plugin`
• chore: bump deps
• perf(language-core): rewrite a subset of template node transforms (#5769)
• chore: bump volar services to 0.0.71 (#6043)
• fix(language-core): do not process inline markdown syntax in semantic-aware segments (#6038)
• v3.2.8 (#6036)
• fix(typescript-plugin): replace language service per-method overrides with a proxy (#6035)
• refactor(language-service): get void elements from default html provider
• refactor(language-core): generate template helper names (#5965)
• chore: bump `reactive-vscode` to 1.0.2
• feat(language-service): support TS module resolution for SCSS `@import` navigation (#6033)
• chore: update tsslint to 3.1.0
• fix(language-core): support navigation for kebab-case declarations in `GlobalComponents` (#6026)
• fix(language-core): replace inline code blocks after sfc blocks processing (#6024)
• chore: upgrade `reactive-vscode` to v1.0.1 (#6019)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)