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

@frankframework/frank-config-layout

v0.0.2

Published

Layout algorithm for Frank configs / flows. WeAreFrank! wishes to use a custom layout algorithm that should look better than images produced by Mermaid. This project assumes that the Frank!Framework can convert Frank configurations or adapters (XML code)

Downloads

4

Readme

frank-config-layout

Layout algorithm for Frank configs / flows. WeAreFrank! wishes to use a custom layout algorithm that should look better than images produced by Mermaid. This project assumes that the Frank!Framework can convert Frank configurations or adapters (XML code) to Mermaid commands. See Mermaid example for the syntax of Mermaid files. This project reads Mermaid text and displays it using a custom algorithm.

The algorithm has not been finished yet. In its current state, the produced drawing does not look like intended. There is a user interface that allows humans to improve the layout. This way, the developers can investigate how to improve the algorithm. A future release of this project should eliminate the need for human intervention.

Development environment and usage

To use this project, please do the following:

  • Clone this project with git clone.
  • Install package manager yarn. Presently we use version 1.22.21.
  • Execute yarn install --immutable.
  • Run the Karma tests with yarn ng test.
  • Run the project with yarn ng serve.
  • Open a webbrowser and go to http://localhost:4200/.
  • In the top-left corner enter some Mermaid text. Here is a simple example.
  • Press "Load with longest path algorithm". See figure below.
  • Try the controls to change the drawing.

Load Mermaid

Publishing

This project is published on npmjs. We publish a service that can produce a static SVG from Mermaid commands. Do the following to publish the next version on npmjs:

  • Ensure that the checkout directory does not contain folder dist.
  • Ensure that all development work has been committed.
  • Run yarn install --immutable.
  • Ensure that your development work has been tested.
  • If you fixed things, commit your work.
  • Run yarn packagr. This should produce folder dist within the checkout directory.
  • Change directory to dist. Then do yarn pack.
  • Publish using yarn publish.
  • Run git tag vX.Y.Z with X.Y.Z the version you just published
  • Run git push vX.Y.Z.
  • Update the version number in package.json for the next release cycle. Commit and push that.