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

@razdolbai/zils

v6.1.11

Published

Z80 and eZ80 assembly language server

Downloads

2,844

Readme

zils

zils is a Language Server for Zilog eZ80 assembly with optional Z80 support. The implementation target is feature parity with ../merls, adapted from Merlin32-style 6502 assembly to Z80-family assembly defined by the official Zilog manuals:

Goals

  • Provide a standalone LSP server over stdio.
  • Default to eZ80 assembly semantics.
  • Allow Z80 semantics (and asMSX directives) through an explicit command-line flag (--asmsx).
  • Work cleanly with coc.nvim through standard language-server configuration.
  • Provide a bundled VS Code extension in vscode/.
  • Match the end-user LSP feature set of ../merls.

Scope

In Scope

  • eZ80 assembly as the default dialect.
  • Z80 assembly as an opt-in dialect selected by CLI flag (--asmsx).
  • Parser-based diagnostics.
  • Cross-file symbol resolution across project sources.
  • The same LSP feature set exposed by ../merls:
    • diagnostics
    • hover
    • completion
    • go to definition
    • find references
    • document symbols
    • workspace symbols
    • semantic tokens
    • rename
    • formatting
    • folding ranges
    • document highlights
    • inlay hints
    • signature help
    • call hierarchy
    • code actions
    • code lens
    • document links
    • selection ranges
  • A standalone npm package usable from coc.nvim.
  • A VS Code extension in vscode/ that bundles the language server.

Out of Scope

  • Non-Zilog CPU families.
  • Assembler backends or binary emission in the initial implementation unless required for extension UX parity.

Planned Technical Direction

  • Runtime: Node.js
  • Language: TypeScript
  • LSP library: vscode-languageserver
  • Process model: standalone stdio server plus bundled VS Code client
  • Default CLI contract: zils --stdio (defaults to ez80)
  • CPU selection contract: zils --stdio --asmsx (switches to z80 mode and enables asMSX directives).

coc.nvim Target

The server should be directly usable from coc.nvim. The intended configuration shape is:

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

An example config lives in examples/coc-settings.json.

VS Code Target

The vscode/ directory should contain an installable Visual Studio Code extension that bundles and launches the server without requiring a separate global install.

Development Rules

  • TDD is required for all implementation work.
  • No task is complete until tests and linting pass completely with no warnings.
  • If behavior, workflow, or scope changes, documentation must be updated in the same task.
  • Do not add separate testing-only tasks to TODO.md; tests belong inside each implementation task.