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

sommark-lsp

v1.0.2

Published

Language Server for SomMark

Readme

SomMark-LSP

Language Server Protocol (LSP) implementation for the SomMark markup language.

Features

  • Diagnostics: Accurate syntax error reporting with precise ranges.
  • Semantic Highlighting: Perfect token-based coloring in any editor that supports LSP Semantic Tokens (VS Code, Neovim, CoC).
  • Easy Sharing: Install globally to use across all editors with a single command.

Installation

Go to the SomMark-LSP directory and install the server globally:

npm install -g sommark-lsp

This will register the sommark-lsp command.

Editor Integration

Vim (coc.nvim)

Add the following to your coc-settings.json:

{
  "languageserver": {
    "sommark-lsp": {
      "command": "sommark-lsp",
      "args": ["--stdio"],
      "filetypes": ["sommark", "smark"],
      "rootPatterns": ["package.json", ".git"]
    }
  },
  "semanticTokens.enable": true
}

And add these to your .vimrc:

autocmd BufRead,BufNewFile *.smark set filetype=sommark
hi link CocSemKeyword Keyword
hi link CocSemString String
hi link CocSemVariable Identifier

Neovim

Use nvim-lspconfig or manually:

vim.lsp.start({
  name = 'sommark-lsp',
  cmd = {'sommark-lsp', '--stdio'},
  root_dir = vim.fs.dirname(vim.fs.find({'package.json', '.git'}, { upward = true })[1]),
})

Helix

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

[language-server.sommark-lsp]
command = "sommark-lsp"
args = ["--stdio"]

[[language]]
name = "sommark"
scope = "source.sommark"
file-types = ["smark"]
language-servers = [ "sommark-lsp" ]

[!NOTE] Helix support is currently limited; diagnostics and some features work, but full syntax highlighting requires a Tree-sitter grammar (coming soon).

Configuration

You can configure the LSP behavior via smark.config.js in your project root.