Skip to content

Component resolution randomly broken, and output of Typescript gives: TSServer exited. [...] SIGTERM #5203

Closed
@stouch

Description

@stouch

Vue - Official extension or vue-tsc version

latest

VSCode version

latest

Vue version

latest

TypeScript version

latest

System Info

package.json dependencies

Steps to reproduce

I got my Vue project component resolution that randomly stops to work.

When I open the Typescript output, it gives:

2025-02-20 17:36:52.495 [info] <semantic> Forking... 2025-02-20 17:36:52.495 [info] <semantic> Starting... 2025-02-20 17:36:52.527 [error] TSServer exited. Code: null. Signal: SIGTERM 

I found this thread : #4215.

So I tried:

 "vue.server.hybridMode": false

in the VSC settings.yml.

And it looks like now everything is fine.

I close this thread, but not sure it'll resolve it permanently.

What is expected?

It's expected to have a VSC + Volar + Typescript environment that works and resolves components.

What is actually happening?

VSC does not resolve components, at random moments, as soon as I start VSC or open some random Vue files.

Link to minimal reproduction

No response

Any additional comments?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions