v3.0 Preview

[johnsoncodehk]

3.0.0-alpha.0 (2025-03-08)

• Change History: v2.2.8...v3.0.0-alpha.0
• VSIX: https://github.com/vuejs/language-tools/actions/runs/13729716065/artifacts/2713802936
• Insiders Edition (sponsor only): https://github.com/volarjs/insiders/releases/tag/v3.0.0-alpha.1

3.0.0-alpha.2 (2025-03-17)

• Change History: v3.0.0-alpha.0...v3.0.0-alpha.2
• VSIX: https://github.com/vuejs/language-tools/actions/runs/13885330341/artifacts/2760442655
• Insiders Edition (sponsor only): https://github.com/volarjs/insiders/releases/tag/v3.0.0-alpha.3

3.0.0-alpha.4 (2025-04-08)

• Change History: v3.0.0-alpha.2...v3.0.0-alpha.4
• VSIX: https://github.com/vuejs/language-tools/actions/runs/14336873818/artifacts/2903994424
• Insiders Edition (sponsor only): https://github.com/volarjs/insiders/releases/tag/v3.0.0-alpha.5

[Satont]

Amazing work.

Is there webstorm build? Not sure does it even possible.

[johnsoncodehk]

@Satont I think that's promising, @tomblachut has already confirmed the required adjustments!

[Ilanaya]

I see you've made some changes to language service plugins here. Would you be able to support working with custom language service plugins in v3? I mean reintroduce changes from #1028 to make volar/services work again?

Related issue

[johnsoncodehk]

@Ilanaya LS plugin support is part of the 3.0 plan, but will not be supported via the reintroduction of volar.config.js.

[rodrigocfd]

I just tested 3.0.0-alpha.2, and it looks pretty good. I found no bugs so far.

[qiaozhu]

何时发布3.0版本

[spaceemotion]

I just installed alpha 3 and for some reason, the auto-complete is missing props on some components and seems incorrect?

Edit: I just checked with v2.2.8 and see the prop show up there just fine.

[KazariEX]

@spaceemotion please provide a minimal reproduction.

[ehoogeveen-medweb]

Tried out alpha 2 with VSCode Remote Development (over SSH), but it seems to often cause the connection to close. It seems to reliably trigger when I go to view the extensions pane, but I've seen it happen seemingly at random too. I tried checking the logs on the remote, but all I could find was this:

exthost25/remoteexthost.log:
2025-04-02 10:48:41.095 [info] Extension host terminating: received terminate message from renderer

remoteagent.log:
2025-04-02 10:48:43.850 [info] [<unknown>][05fc3261][ExtensionHostConnection] <792972> Extension Host Process exited with code: 0, signal: null.

Here exthost25 is just the most recent extension host. So it seems like a renderer crash, but no further information is given (no stack or error code).

Using VSCode v1.98.2 and Remote SSH v0.118.0 (both the latest as of right now), a Windows host and a Linux remote (but it seems to be the remote that crashes).

[hkochniss]

that sounds awesome.. roughly when can we expect a release in VS market place? :)

[KazariEX]

Since semver pre-release tags are not supported on VSCode, we can't release these alpha versions at the moment.

Before the official version is released, we need to patiently wait for other editors to integrate the new architecture.

[hkochniss]

So basically waiting for Jetbrains here to adjust their plugin API, ok