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

schesign-graph-examples

v0.0.12

Published

Various graphs used in schesign

Downloads

7

Readme

Central locations for graphs used for testing

Import graphs can be uploaded as a design. Export graphs are returned when a design is downloaded. They include defaults, external node resolution, validation, etc.

*** Fix, this is not longer true *** Import graphs can point to nodes in other designs using a url identifier. An export graph will contain the evaluation of those urls. Also new nodes in an import graph will not have uids yet.


propertyVariations

One of every propertySpec constraint One of every rangeType One of every rangeConstraint

recursion

Simple case to ensure nestedObjects can have children that reference themselves

testInhertiance

  • 2 different designs are used to test inheritance chain.
  • Exclude parent properties should be tested class1 "a1", "a2", "a3" should all be overwritten and not make it to class5 in inheritance_chain_2
  • Override property should be tested. Property "a" is in parent design and child design. Class 5 should use the lowest in the chain, "a" type Boolean

testLinking

  • Test propertySpecs pointing to internal and external properties
  • Test LinkedClass ranges pointing to internal and external classes
  • Test more then one class pointing to same property (linked_nodes_1 property a)
  • Test a class should be able to have a property with range that points to itself (linked_nodes_1 class2 property a)
  • An imported NestedObject should be able to point to classes and and properties in parent design (linked_node_1 property b) and these should be resolved
  • Should be able to import classes and properties into version and their dependencies should resolve (Linked Nodes 2)
  • Class 2 should be a direct import
  • Property f should be a direct import
  • Property d should be imported through Class 3 through Property f