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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@allnulled/jsontyped

v1.0.2

Published

JSON extension to support external types

Readme

jsontyped

To support types in JSON.

Installation

npm i -s @allnulled/jsontyped

Importation

In node.js:

require("@allnulled/jsontyped");

In html:

<script src="node_modules/@allnulled/jsontyped/jsontyped.js"></script>

Usage

JsonTyped.parse(`"This could be a normal JSON"`);
JsonTyped.parse(`@message "This is another level of JSON"`);
JsonTyped.parse(`@deeper.types "This is a valid way of chaining ref types"`);
JsonTyped.parse(`@deeper/types/somewhere/else.js "This is also a valid way of chaining ref types"`);
JsonTyped.parse(`@file:///you/can/specify/protocol/too "This is also a valid way of chaining ref types"`);
JsonTyped.parse(`@http:///you/can/specify/protocol/too "This is also a valid way of chaining ref types"`);

Basically, any type supports this "prefix" in which you specify, with these symbols and normal variable-accepted js symbols [A-Za-z_$] +[0-9].

Then it always translate the types to:

{
  $protocol: null,
  $type: "message",
  $value: "This is another level of JSON"
}

Which is also quite readable. You can customize the output re-building the parser, by npm run build.

Changelog

22 of January of 2025.

  • Accepts URLs with protocol, host, path, querystring and section automatically parsed.
  • Accepts also JavaScript object paths separated by ".".