Skip to content

Vue LSP not reporting diagnostics #2756

Closed as not planned
Closed as not planned

Description

@drevantonder

TL;DR Vue LSP is not reporting diagnostics. Fix is in #2097


I created #1952 just as @vue/language-tools v3 was released. This meant that Vue worked briefly (if at all) until it automatically updated to v3.

I fixed this by upgrading to v3 and correctly integrating with the typescript LSP in #2097. It hasn't been merged yet, but it has worked locally since.

Created this issue to bump the PR and just give a heads up that the Vue LSP does not work atm.

Love the work you guys are doing! opencode has been my daily driver for a while now! Thanks!

Activity

  1. github-actions commented on Sep 24, 2025

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    Feel free to ignore if none of these address your specific case.

  2. self-assigned this
    on Sep 24, 2025
  3. rekram1-node commented on Sep 24, 2025

    @rekram1-node
    Collaborator

    ty ill check out pr

  4. daleal commented on Oct 28, 2025

    @daleal

    This PR merged would be great! I love the LSP feature of opencode and I am missing it so much in Vue :( ❤️

  5. rekram1-node commented on Oct 28, 2025

    @rekram1-node
    Collaborator

    sorry this fell under the radar, ill check it out today

  6. daleal commented on Nov 4, 2025

    @daleal

    I know this week has been crazy af with the release of 1.x.x, so I am giving this a bump just so it doesn't get lost. Thank you! ❤️

  7. rekram1-node commented on Nov 4, 2025

    @rekram1-node
    Collaborator

    @daleal definitely acknowledged, just hard I need to resolve some merge conflicts for it and verify it works so once I find some time i can take more of a look, it just has had conflicts

  8. drevantonder commented on Nov 4, 2025

    @drevantonder
    ContributorAuthor

    @daleal definitely acknowledged, just hard I need to resolve some merge conflicts for it and verify it works so once I find some time i can take more of a look, it just has had conflicts

    I'll see if I can get a chance to update the PR. Busy season/week for me atm with getting married, but would absolutely love to see this merged. 😆

  9. rekram1-node commented on Nov 4, 2025

    @rekram1-node
    Collaborator

    @drevantonder congrats!!!!

  10. drevantonder commented on Nov 6, 2025

    @drevantonder
    ContributorAuthor

    @daleal definitely acknowledged, just hard I need to resolve some merge conflicts for it and verify it works so once I find some time i can take more of a look, it just has had conflicts

    I'll see if I can get a chance to update the PR. Busy season/week for me atm with getting married, but would absolutely love to see this merged. 😆

    Sadly not looking like I'll have the time. I'll return December and update then if still pending.

  11. daleal commented on Nov 8, 2025

    @daleal

    Congrats @drevantonder!!! I opened this PR that is basically the exact same code you uploaded (I tested locally that the fix works too) but without the conflicts!

  12. drevantonder commented on Dec 21, 2025

    @drevantonder
    ContributorAuthor

    Thanks @daleal! 😊 I have returned and was going to work on it if it wasn't already done. Will reply more on the PR.

  13. AlejandroAkbal commented on Mar 14, 2026

    @AlejandroAkbal

    Any progress?

  14. github-actions commented on May 14, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions