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

@iriograph/rdf-io

v0.12.3

Published

Framework-independent RDF dataset import, merge, rebase, and semantic export for Iriograph.

Readme

@iriograph/rdf-io

日本語

@iriograph/rdf-io is a framework-independent boundary for importing Turtle or JSON-LD into an RDF dataset, previewing a new document or merge, applying the result atomically, explicitly rebasing a namespace, and exporting semantic RDF only.

Install

npm install --save-exact @iriograph/rdf-io

Import and merge

import {
  applySemanticPatch,
  importRdfDataset,
} from "@iriograph/rdf-io";

const preview = await importRdfDataset({
  format: "text/turtle",
  source: externalTurtle,
  baseIri: "urn:portable:fallback:",
  target: {
    kind: "merge",
    existing: currentDataset,
    localIriNamespace: "urn:workspace:diagram:",
  },
});

if (preview.valid && preview.patch) {
  const result = applySemanticPatch(currentDataset, preview.patch);
  if (result.accepted) currentDataset = result.dataset;
}

The candidate contains expanded RDFJS quads, a semantic diff, validation diagnostics, dataset statistics, local IRI collisions, and a loss report. Literals retain their exact lexical value, language, and datatype. Untagged values stay untagged; no profile or locale default is applied.

Duplicate statements are reported and represented once because an RDF dataset has set semantics. Imported blank node labels are scoped away from existing blank nodes during merge. Remote JSON-LD contexts are not fetched implicitly.

Local identity joins are rejected by default. Set localIriCollisionPolicy: "merge" only when the shared expanded IRIs are intentionally the same resources. External expanded IRIs are never rewritten to the local namespace.

Explicit rebase

import { createExplicitRebase } from "@iriograph/rdf-io";

const rebase = createExplicitRebase({
  dataset: importedDataset,
  fromNamespace: "urn:source:diagram:",
  toNamespace: "urn:workspace:copy:",
});

Rebase is deliberately a separate public API. It previews every expanded IRI change, rejects target collisions, and returns the same fingerprint-bound atomic patch shape as import. IRIs outside fromNamespace remain unchanged.

Semantic export

import { exportRdfDataset } from "@iriograph/rdf-io";

const turtle = await exportRdfDataset({
  dataset: currentDataset,
  format: "text/turtle",
});
const jsonLd = await exportRdfDataset({
  dataset: currentDataset,
  format: "application/ld+json",
});

Export accepts only an RDF dataset, so geometry, routing, icons, colors, viewport state, and other view overlay data cannot enter the RDF output. Turtle export rejects named graphs instead of dropping graph identity; JSON-LD can preserve a complete RDF dataset. The loss report distinguishes non-semantic syntax/shape changes from RDF semantic loss.

License

MIT. Third-party components retain the licenses listed in THIRD_PARTY_NOTICES.md. See LICENSE.