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

webgme-taxonomy

v1.2.2

Published

## Installation

Downloads

11

Readme

webgme-taxonomy

Installation

First, install the webgme-taxonomy following:

Second, start mongodb locally by running the mongod executable in your mongodb installation (you may need to create a data directory or set --dbpath).

Then, run webgme start from the project root to start . Finally, navigate to http://localhost:8888 to start using webgme-taxonomy!

Creating a Taxonomy

The easiest way to create a taxonomy is to simply import a CSV file. Here are the steps:

  • First, create a taxonomy in a spreadsheet where properties have (text), (int), (bool), (enum), (set), etc, appended to the given property name. Each child term/property should be on a line below the parent and indented by 1 cell. Next, export the page as a CSV. An example as a CSV is shown below:
    parentTerm,,,
    ,childTerm,,,
    ,,name (text),
    ,,age (int),
    ,,color (enum),
    ,,,red
    ,,,blue
    ,,,green
  • Next, use ./bin/taxonomy-from-csv <path-to-csv> > taxonomy.json to generate a JSON representation that can be imported into the environment.
  • Create a new project in the design studio and import the taxonomy seed as a library.
  • Create a new Taxonomy node in the root node.
  • Enable the SetStateFromJSON plugin for this new node.
  • Run SetStateFromJSON on this new Taxonomy node with the taxonomy.json file generated in the second step.
  • All done!

Integrated Tools

There are a few integrated tools in the design studio which are automatically configured using projects in the design studio:

  • Search Dashboard: This is a web-based dashboard for viewing data associated with terms in the taxonomy. Currently, only Microsoft Premonition Data Platform is supported to store artifacts but this shouldn't be hard to generalize. (Generalization has been the hopes :).)
  • Taxonomy Term Creator (Form): This is a web-based form for selecting terms given the taxonomy defined in the studio.

Misc To Do

  • [ ] use it for webgme libraries?
    • publish from within webgme
    • define a taxonomy
    • storage adapter?
      • mongodb, right?
        • MongoDB+Blob
      • configuration opts:
        • collection name
          • validation so not colliding with others