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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@explorablegraph/symbols

v0.0.2-d

Published

Well-known Symbol objects for the explorable graph ecosystem

Downloads

14

Readme

This package does nothing other than define a handful of JavaScript Symbol objects which form the bedrock of the explorable graph ecosystem in JavaScript.

With these symbols, you can create explorable objects on your own that are compatible with this ecosystem. You could also create symbols of your own and build out your own explorable ecosystem (but the explorable objects in your ecosystem would not be directly compatible with the others defined in this project.)

The symbols are defined in a package of their own so that you can adopt the explorable function pattern in any JavaScript project with no other dependencies. You do not have to use the core exfn package.

Hypothetically, the symbols defined here could someday be defined in the JavaScript language itself. If that came to pass, this package could simply re-export the new, standard JavaScript symbols. All explorable objects built with this project would then become compatible with those created with the standard symbols.