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

lezer-shexc

v0.1.0

Published

Incremental, error-tolerant Lezer grammar for ShEx Compact Syntax (ShExC), with CodeMirror highlighting tags

Readme

lezer-shexc

An incremental, error-tolerant Lezer grammar for ShEx Compact Syntax (ShExC), with highlighting tags for CodeMirror 6.

import {parser} from "lezer-shexc";
const tree = parser.parse(schemaText);   // a @lezer/common Tree

The grammar follows the ShExC grammar in the ShEx specification, in the LALR shape shex.js's own parser gives it, so what parses here is what the validator accepts: every schema in the ShEx test suite parses without an error node, and a schema the validator refuses shows where. Being Lezer, a half-typed schema still parses around the error, and an edit re-parses only what it touched.

This is the editor's parse -- colour, folding, bracket matching, the structure under the cursor. The schema itself still comes from @shexjs/parser; @shexjs/editor-services uses both.

src/parser.js is generated from src/shexc.grammar by npm run build (@lezer/generator).

Development

git clone https://github.com/shexjs/lezer-shexc.git
cd lezer-shexc
npm install      # also runs `prepare`, i.e. `npm run build`
npm test

The tests run the grammar over the ShEx test suite (schemas/ must parse clean, negativeSyntax/ must not), which npm install fetches as the shex-test devDependency. To test against a checkout instead, name it: SHEX_TEST=../shexTest npm test.

src/parser.js and src/parser.terms.js are committed so that the package installs from git without a build step; regenerate them (npm run build) in the same commit as a change to src/shexc.grammar -- CI checks that they match.

Maintained alongside shex.js by the same people; issues and pull requests about the grammar belong here.