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 🙏

© 2026 – Pkg Stats / Ryan Hefner

skir-language-server

v0.1.0

Published

Language Server Protocol implementation for the Skir schema language (Vim, Neovim, Emacs, ...)

Readme

Skir Language Server

A Language Server Protocol (LSP) implementation for the Skir schema language. Enables IDE features in Vim, Neovim, Emacs, and any other LSP-aware editor.

Features

| Feature | Description | |---|---| | Diagnostics | Syntax and type errors, config validation, and breaking-change warnings (when a snapshot is present) | | Go to definition | Jump to the declaration of any type, field, constant, or method | | Find references | List every usage of a symbol across the workspace | | Hover | Show documentation comments for records, fields, methods and constants | | Completion | Context-aware completions with auto-import of types from other modules | | Rename | Rename a symbol and update all references across the workspace | | Formatting | Format the current .skir file on save or on demand | | File rename | Automatically update import paths in other files when a .skir file is renamed (via willRenameFiles) |

Requirements

  • Node.js ≥ 22.12.0 (required for require() of ES modules used by the Skir compiler)
  • A Skir workspace with a skir.yml file

Installation

npm install -g skir-language-server

Or use it locally inside a project:

npm install --save-dev skir-language-server

Usage

The server communicates over stdio (the standard mode used by most editors):

skir-language-server --stdio

Or directly via npx without a global installation:

npx skir-language-server --stdio

Editor configuration

Neovim (nvim-lspconfig)

Add the following to your Neovim configuration (e.g. ~/.config/nvim/lua/plugins/skir.lua):

local lspconfig = require("lspconfig")
local configs = require("lspconfig.configs")

if not configs.skir then
  configs.skir = {
    default_config = {
      cmd = { "npx", "skir-language-server", "--stdio" },
      filetypes = { "skir" },
      root_dir = lspconfig.util.root_pattern("skir.yml"),
      settings = {},
    },
  }
end

lspconfig.skir.setup({})

You also need a filetype detection rule. Add to ~/.config/nvim/lua/filetypes.lua (or filetype.vim):

vim.filetype.add({ extension = { skir = "skir" } })

Neovim (using mason-lspconfig or manual setup)

vim.api.nvim_create_autocmd("FileType", {
  pattern = "skir",
  callback = function()
    vim.lsp.start({
      name = "skir",
      cmd = { "npx", "skir-language-server", "--stdio" },
      root_dir = vim.fs.dirname(vim.fs.find("skir.yml", { upward = true })[1]),
    })
  end,
})

coc.nvim

Add to your coc-settings.json:

{
  "languageserver": {
    "skir": {
      "command": "npx",
      "args": ["skir-language-server", "--stdio"],
      "filetypes": ["skir"],
      "rootPatterns": ["skir.yml"]
    }
  }
}

Vim (vim-lsp)

if executable('npx')
  au User lsp_setup call lsp#register_server({
    \ 'name': 'skir',
    \ 'cmd': {server_info -> ['npx', 'skir-language-server', '--stdio']},
    \ 'whitelist': ['skir'],
    \ })
endif

Also add filetype detection if .skir is not yet recognized:

autocmd BufRead,BufNewFile *.skir setfiletype skir

Emacs (eglot)

(add-to-list 'auto-mode-alist '("\\.skir\\'" . skir-mode))
(with-eval-after-load 'eglot
  (add-to-list 'eglot-server-programs
               '(skir-mode . ("npx" "skir-language-server" "--stdio"))))

Emacs (lsp-mode)

(lsp-register-client
 (make-lsp-client
  :new-connection (lsp-stdio-connection '("npx" "skir-language-server" "--stdio"))
  :major-modes '(skir-mode)
  :server-id 'skir-ls))

Helix

Add to ~/.config/helix/languages.toml:

[[language]]
name = "skir"
scope = "source.skir"
file-types = ["skir"]
roots = ["skir.yml"]
language-servers = ["skir-language-server"]

[language-server.skir-language-server]
command = "npx"
args = ["skir-language-server", "--stdio"]

Sublime Text (LSP package)

In Preferences → Package Settings → LSP → Settings, add:

{
  "clients": {
    "skir": {
      "command": ["npx", "skir-language-server", "--stdio"],
      "enabled": true,
      "selector": "source.skir"
    }
  }
}

How it works

The server scans the workspace for:

| File | Purpose | |---|---| | skir.yml | Workspace definition and dependency declarations | | skir-src/**/*.skir | Source modules | | skir-snapshot.json | Snapshot baseline for breaking-change detection | | skir-external/dependencies.json | Pre-downloaded external dependency modules |

It uses the same compiler internals as the official Skir CLI (skir npm package) to parse, type-check, and resolve all modules. Diagnostics are published as LSP textDocument/publishDiagnostics notifications.


Building from source

npm install
npm run build

The compiled server is at dist/server.js.

skir-language-server