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

@shexjs/term

v1.0.0-alpha.29

Published

Shape Expressions triple expression evaluator - simple regexp returning 1 error.

Readme

@shexjs/term

npm version CI

RDF terms as ShEx uses them: conversions between RDF/JS terms, ShExJ's JSON-LD-style values, and Turtle lexical forms — plus the Start sentinel and the string-unescaping shared by the ShExC and ShapeMap parsers.

Install

npm install @shexjs/term

Quick start

const Term = require("@shexjs/term");
const {DataFactory} = require("n3");

// RDF/JS term → ShExJ value (an IRI is a string; a literal is an object)
Term.rdfJsTerm2Ld(DataFactory.namedNode("http://a.example/n1"));
// 'http://a.example/n1'
Term.rdfJsTerm2Ld(DataFactory.literal("chat", "fr"));
// { value: 'chat', language: 'fr' }

// … and back
Term.ld2RdfJsTerm({value: "chat", language: "fr"});
// a Literal RDF/JS term for "chat"@fr

// either form → Turtle lexical form
Term.rdfJsTerm2Turtle(DataFactory.literal("chat", "fr"));   // '"chat"@fr'
Term.shExJsTerm2Turtle("http://a.example/n1");              // '<http://a.example/n1>'

What's here

  • rdfJsTerm2Ld(term) / ld2RdfJsTerm(ld) — between RDF/JS terms and the values ShExJ writes (IRI as string, _:‑prefixed blank node, literal as {value, type?, language?}).
  • rdfJsTerm2Turtle(term, meta?) / shExJsTerm2Turtle(term, meta?) — render a term in Turtle, abbreviating with meta's base and prefixes when given.
  • Start / isStart(x) — the sentinel a shape map uses to say "the schema's start shape": {node, shape: Start}. There is one frozen Start object; isStart also recognizes a structural clone ({term: "START"}), which is what survives a postMessage across a worker boundary.
  • unescapeText(string, replacements) — the \uXXXX/\U… (and caller-supplied) escape decoding that the ShExC and ShapeMap grammars share.
  • RdfLangString, XsdString — the two implicit literal datatypes.
  • Terminals — regular expressions for RDF terminal productions (IRIREF, PNAME_LN, …).
  • Types used across the suite: SchemaIndex, ShapeMapEntry, Meta and friends.

This package sits under everything else in the suite (the parsers, the validator, the neighborhoods), so it is versioned independently and depends on nothing else in it.


@shexjs/term is one of the shex.js packages; installing shex pulls in the whole suite, and its README maps them.