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

@bptlab/openbpt-modeler-er

v1.0.0

Published

ER modeler based on diagram-js for use in the OpenBPT platform.

Readme

openbpt-modeler-template

Template repository for the creation of modelers used in the OpenBPT project. The template is a generalization of the ptn-js modeler. It is based on diagram-js and took inspiration from bpmn-js, object-diagram-js and fcm-js.

The template showcases a working version of a basic Petri net modeler whose elements should be replaced with the elements of the new modeling language. For that purpose, fork the repository and follow the steps outlined below. If you create a new modeler and implement additional features that could be generalized to fit any modeler, please feel free to create a pull request so that others may profit from your extension as well!

Development Setup

Link to demo-repo using npm link:

  • run npm link in the current repository directory
  • switch to demo repository
  • run npm i
  • run npm link <name-of-your-new-modeler>

Implementing a New Modeler

Implementing a new modeler requires the definition of the metamodel of the modeling language, a custom renderer, a set of icons, and a few adaptations in the modeler itself. In general, the keyword CustomModelerTodo marks places in the code that require adaptation.

Defining the Metamodel

To define the model structure, we build on moddle, which uses a schema defined as a JSON file to create a meta model that can be used to instantiate model elements while knowing their attributes and relations and provides a structure for importing and exporting XML files. The followning class diagram shows the currently implemented metamodel used in the modeler. It can be generally divided into two sides:

  • The semantic elements are the classes on the left, everything inheriting from Schema. They define the different model elements and their attributes/relations.
  • The syntactic elements are the classes on the right, everything inheriting from DiagramElement as well as Diagram and Plane. These elements are visual representatoions of the model elements, including positional information and associated labels.

Moddle_Class_Diagram

In most cases, it should not be necessary to modify the metamodel of the syntactic elements. For the semantic elements, the classes inheriting from Node and BinaryConnection (marked in red) must be defined for the respective modeling language in modelSchema.js. A documentation can be found here. Setting isAttr for a property will include it as an attribute in the XML, otherwise it is a separate child-tag.

Creating a Custom Renderer

Adding Icons

Adapting the Modeler