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

jalhyd

v4.18.0

Published

JaLHyd, a Javascript Library for Hydraulics

Downloads

328

Readme

JaLHyd - Javascript Library For Hydraulics

See also developers documentation

Build and release

Requirements

  • nodejs

Install dependencies

npm install

Run unit tests using Jasmine

Debugging might not be possible because of circular dependencies generated by typescript compiler

npm run jasmine

Compile (es2015 modules)

This is the preferred way of compiling, notably for usage in Web apps (ngHyd)

npm run build

Compile for Node.js (commonjs modules)

Use this if you want to write a CLI application in JS or TS, that will be executed by Node.js (see examples in /boilerplate)

npm run build-node

Generate release package (es2015 modules)

npm run package

Generate release package for Node.js (commonjs modules)

npm run package-node

Flag suspicious language usage

npm run lint

Generate typedoc

npm run doc

Generate UML diagram

The tsviz package can be used for drawing class diagram of the current code.

To install tsviz:

npm install -g tsviz

There's currently a bug on debian like distribution due to a wrong declaration of graphviz path in the code: https://github.com/joaompneves/tsviz/issues/5 To work around, you can create a link to the good path: sudo ln -s /usr/bin/dot /usr/local/bin/dot

To draw the diagram:

npm run viz

Release policy

Use semantic versioning.

When releasing a Cassiopee (NgHyd) version along with a JaLHyd version, it's discouraged to execute release steps manually, see "Release Policy / Release Script" in NgHyd's README.md

Before releasing a new stable version, one should complete the following files

  • CHANGELOG.md
  • package.json (update "version", or use npm version)

Every stable version should be tagged with both

  • a tag stating compatibility with NgHyd, of the form nghyd_X.Y.Z
  • the stable tag

The stable tag should be set after the NgHyd compatibility tag, so that git describe returns stable (latest tag). There should be at least 1s between the two tag commands, so that date sorting is not confused.

Here are the steps to follow for an example 4.5.0 version

npm version 4.5.0
# commit changes

git tag -fa nghyd_4.5.0
sleep 1
git tag -fa stable
git push --tags --force