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

@williamcachamwri/markui-language-service

v0.2.0

Published

Editor-neutral diagnostics, completions, hover, and quick fixes for MarkUI Markdown

Readme

@williamcachamwri/markui-language-service

Editor-neutral diagnostics, completions, hover information, and safe quick fixes for MarkUI Markdown.

Install

npm install @williamcachamwri/markui-language-service

Create a service

import { createMarkUILanguageService } from '@williamcachamwri/markui-language-service'

const service = createMarkUILanguageService()

The service uses the same compiler and directive validator as the Vite plugin and CLI. Editor results therefore match markui check and production builds.

Diagnostics

const diagnostics = service.validate(source, '/workspace/src/pages/index.md')

Diagnostics include the stable MarkUI code, severity, filename, line, column, source range, and repair hint where available.

Completions

const items = service.complete(source, {
  line: 4,
  column: 8,
})

Completion items cover:

  • leaf and container directive names;
  • unused component properties;
  • enum values from component schemas;
  • schema details and insertion text.

Positions are one-based to match MarkUI diagnostics.

Hover

const hover = service.hover(source, {
  line: 4,
  column: 6,
})

Hover results describe a component or property and return the exact source range under the cursor.

Quick fixes

for (const diagnostic of service.validate(source)) {
  const fixes = service.codeActions(source, diagnostic)
}

The initial safe fixes cover:

  • closing an unclosed container;
  • removing an unexpected closing marker;
  • converting a leaf component from ::: to :: syntax.

The service intentionally returns no edit when a repair cannot be made safely.

Custom component registry

import { ComponentRegistry } from '@williamcachamwri/markui-core'
import { createMarkUILanguageService } from '@williamcachamwri/markui-language-service'

const registry = new ComponentRegistry([
  {
    name: 'hero',
    allowChildren: true,
    description: 'Page hero section',
    props: {
      tone: {
        type: 'string',
        enum: ['light', 'dark'],
      },
    },
  },
])

const service = createMarkUILanguageService({ registry })

Custom registries affect validation, completions, and hover information consistently.