Skip to content

[Bug]: Activating extension 'vscode.typescript-language-features' failed: Could not find bundled tsserver.js #5019

Closed

Description

@hanf2x

Is there an existing issue for this?

  • I have searched the existing issues

OS/Web Information

  • Web Browser: google chrome
  • Local OS: ubuntu
  • Remote OS: ubuntu
  • Remote Architecture: amd64
  • code-server --version: 1.64.2

Steps to Reproduce

  1. yo code to create a new vscode plugin
  2. Start debug the extension
  3. vscode in new window shows
Activating extension 'vscode.typescript-language-features' failed: Could not find bundled tsserver.js
VS Code's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VS Code
Source: Typescript and Javascript Language Features (Extension)

Expected

should not happen

Actual

  1. vscode in new window shows
Activating extension 'vscode.typescript-language-features' failed: Could not find bundled tsserver.js
VS Code's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VS Code
Source: Typescript and Javascript Language Features (Extension)

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code?

  • I cannot reproduce this in VS Code.

Are you accessing code-server over HTTPS?

  • I am using HTTPS.

Notes

I had tried to go into /usr/lib/code-server and run yarn, but no luck, where is tsserver.js?

Activity

  1. added
    bugSomething isn't working
    triageThis issue needs to be triaged by a maintainer
    on Mar 23, 2022
  2. imwux commented on Mar 23, 2022

    @imwux

    I have the same issue

  3. jsjoeio commented on Mar 23, 2022

    @jsjoeio
    Contributor

    I cannot reproduce on macOS

    image

    where is tsserver.js

    Could be this file 🤔 but not 100% sure:
    https://github.com/microsoft/vscode/blob/main/extensions/typescript-language-features/src/tsServer/server.ts

    VS Code's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VS Code
    Source: Typescript and Javascript Language Features (Extension)

    Do you have a firewall or virus tool installed? And did you try reinstalling the extension like it suggests?

  4. jsjoeio commented on Mar 23, 2022

    @jsjoeio
    Contributor

    More info here maybe: microsoft/vscode#72721

  5. gghub77 commented on Mar 23, 2022

    @gghub77

    This was missing /usr/lib/code-server/lib/vscode/extensions/node_modules/typescript/lib , it affected vscode.typescript-language-features looking for tsserver.js and html-language-features looking for typescript.js . I took the typescript dir from another install and no more errors

  6. jsjoeio commented on Mar 23, 2022

    @jsjoeio
    Contributor

    @code-asher does this ring a bell? It seems very odd that we would be missing one file.

    Otherwise I can look into it. I couldn't reproduce though.

  7. matt-teix commented on Mar 23, 2022

    @matt-teix

    Also have this issue after updating this morning

  8. pauromateusu commented on Mar 23, 2022

    @pauromateusu

    Also had the issue updating It now. 4.1.0 seems to work fine. Using userLAnd, Ubuntu and install.sh

  9. gghub77 commented on Mar 23, 2022

    @gghub77

    node_modules/typescript

    The whole typescript dir wasn't there for me under node_modules

  10. jsjoeio commented on Mar 23, 2022

    @jsjoeio
    Contributor

    Wow...I wonder if it's Linux only then 🤔

    For anyone else having this issue, please give a 👍🏼 to the first comment so we can gauge how many people are affected by this.

  11. added
    needs-investigationThis issue needs to be further investigated
    high-priorityThis issue needs to be resolved ASAP
    and removed
    triageThis issue needs to be triaged by a maintainer
    on Mar 23, 2022
  12. added this to the April 2022 milestone on Mar 23, 2022
  13. 15 remaining items

  14. jsjoeio commented on Mar 28, 2022

    @jsjoeio
    Contributor

    @code-asher any ideas on this? Did we forget something in one of our patches?

  15. added a commit that references this issue on Mar 29, 2022
    073ea27
  16. added 3 commits that reference this issue on Mar 29, 2022
    d3c42c3
    c319eb1
    f228cc9
  17. ZauberNerd commented on Apr 6, 2022

    @ZauberNerd

    @jsjoeio do you plan on releasing a fix version for this or do we need to downgrade to 4.1.0 / wait for 4.3.0?

  18. jsjoeio commented on Apr 6, 2022

    @jsjoeio
    Contributor

    @ZauberNerd yes, this fix will be in the next release!

  19. its-dibo commented on Apr 10, 2022

    @its-dibo

    same here

  20. modified the milestones: April 2022, 4.3.0 on Apr 13, 2022
  21. added a commit that references this issue on Apr 23, 2022
    afb39d9
  22. added a commit that references this issue on Feb 22, 2024
    06e36b4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinghigh-priorityThis issue needs to be resolved ASAP

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions