Pull request #334 · meemalabs/meema

Bumps vue-tsc from 0.2.2 to 0.31.1.

Changelog

<h2>0.31.1</h2>

fix: support type export statements on the top in <script setup> (#886)

<h2>0.31.0</h2>

feat: support generic emits (#877)

feat: support top level await in <script setup> without extra tsconfig setting (#538)

feat: fully support formatting for v-for expression

fix: can't ignore variable unused report by _ prefixes in v-for (#878)

fix: no error when definitions from <script setup> used in <script> (#766)

<h2>0.30.6</h2>

fix: re-support withDefaults for props type in template (#868)

fix: tsconfig report schemas/tsconfig.schema.json missing (#869)

fix: enabled editor.semanticHighlighting.enabled by default to avoid component tag show invalid color when installed some themes

fix: export default expression semicolon breaks component type in script setup (#874)

fix: don't wrap options with defineComponent when convert to setup sugar

Breaking changes

When use <script setup>, ignore extra component options wrapper function (defineComponent / Vue.extends ...)

<h2>0.30.5</h2>

fix: vueCompilerOptions intellisense not working on jsconfig

fix: vue-tsc broken on windows in 0.30.3

<h2>0.30.4</h2>

fix: component tag semantic highlisht token incorrect with folding (#801)

fix: component type broken by withDefaults in 0.30.3

Breaking changes

Unsupported withDefaults for component props type

<h2>0.30.3</h2>

feat: auto wrap () to as expression (v-bind="foo as string" -> v-bind="(foo as string)" (#859)

feat: support tsconfig properties intellisense on take over mode (#833)

feat: support vueCompilerOptions intellisense in tsconfig (#833)

fix: vue-tsc and typescript could't guaranteed found each other (#851)

fix: avoid vue-tsc stripped props jsdoc comments for script setup components (#799)

fix: string source type incorrect in v-for (#839)

Known regressions

component type broken by withDefaults

... (truncated)

Commits

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)