npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

godot-wsl-lsp

v1.1.1

Published

Simple LSP server that converts WSL and Windows paths to Godot LSP

Downloads

14

Readme

Godot WSL LSP

Simple LSP server that sits between Neovim instance on WSL and the Godot LSP server running on Windows.

This server's only purpose is to convert the Windows and WSL path back and forth, to have a seamless experience editing GDScript files on Neovim running inside WSL (while Godot is still running on Windows).

Setup

You can find more information on the entire setup process in this gist.

The updated configuration from the previous gist using this server would be:

-- after/ftplugin/gdscript.lua

local cmd = { "godot-wsl-lsp" }
local pipe = "/tmp/godot.pipe"

vim.lsp.start({
    name = "Godot",
    cmd = cmd,
    filetypes = { "gdscript" },
    root_dir = vim.fs.dirname(vim.fs.find({ "project.godot", ".git" }, {
        upward = true,
        path = vim.fs.dirname(vim.api.nvim_buf_get_name(0))
    })[1]),
    on_attach = function(client, bufnr)
        vim.api.nvim_command('echo serverstart("' .. pipe .. '")')
    end
})

Setup using neovim/nvim-lspconfig

If you're using neovim's official nvim-lspconfig, you can omit setting up the lsp server using the naked vim.lsp API and ftplugin. In this case, the following configuration is recommended:

local lspconfig = require("lspconfig")

lspconfig.gdscript.setup({
    cmd = { "godot-wsl-lsp" },
})

WSL mirrored networking mode

If you're using WSL's 'mirrored' networking mode (supported since WSL 2.0.0, you can use the --useMirroredNetworking flag when starting your lsp server:

cmd = { "godot-wsl-lsp", "--useMirroredNetworking" }

Manually specifying what host to connect

If you prefer, you can also specify the host ip address you wish to connect manually:

cmd = { "godot-wsl-lsp", "--host", "1.2.3.4" }