Skip to content

Change upstream language serverΒ #7

@bollwyvl

Description

@bollwyvl

Thanks for getting this going!

It looks like the current language server [email protected], probably originally chosen in jupyterlab-lsp because it was a single .js file, might never get updated again, and isn't very well documented. It's somewhat hard to know what behavior quirks are due to already-fixed-upstream bugs or (sheepishly) my use of it in environments with jupyterlab-lsp.

The upstream's upstream has been getting updates (currently [email protected], but does not have a single-file distribution.

Perhaps ncc could be used at build time of this package to generate an equivalent single-file distribution, such that no node_modules would be included, only a single json-language-server-bin.

Will do some investigating...

Semi-related: it's probably now appropriate to start dreaming how we'd get high-value language servers like this into jupyterlite... jupyterlite/jupyterlite#390 (comment)

Metadata

Metadata

Assignees

No one assigned

    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