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

decision-maker

v1.0.0

Published

The flow decision making module for the ArborKnot Collection System"

Downloads

5

Readme

Business Logic

The business logic all of the smart algorithms and decisions will be here

Resources

Getting Started

Install:

Open a terminal and run:

git clone [email protected]:Arborknot/business-logic.git
cd business-logic
cp .env.example .env # modify .env
nvm use
npm install
npm run dev

Then go to http://localhost:3000.

Scripts

| Script | Description | | ----------------- | -------------------------------- | | npm run test | Run tests | | npm run ci-test | Run tests in CI mode | | npm run build | Build project | | npm run start | Run server for production | | npm run dev | Run server for dev | | npm run watch | Run server for dev in watch mode |

Environment Variables

The following table contains full list of used environment variables:

| Var | Description | Default | Example | | ----------------------------------- | ----------------------------------- | --------- | --------------------- | | PORT | Server port | 3001 | See default | | DB_HOST | DB's host | localhost | See default | | DB_PORT | DB's port | 5432 | See default | | DB_NAME | DB's name | postgres | See default | | DB_SCHEMA | DB's schema | public | See default | | DB_USERNAME | DB's user | postgres | | | DB_PASSWORD | DB's password | X | | | MESSAGE_MANAGER_INTERNAL_ENDPOINT | The endpoint of the message manager | X | http://localhost:3006 |

Also see (logger's configuration](https://github.com/Arborknot/logger).

Note: .env.example can be used as a reference too.

Runtime Variables

In service config there should be a row named business-logic, the json next to it can contain the following vars

| Var | Description | Default | Example | | -------------- | -------------------------------------------------------------------- | ------- | ------------- | | LOGGER_LEVEL | The level of the log | info | See default | | TEST_MODE | When true the the service will not send a request to message manager | false | See default |

Tips :bulb:

Automatically nvm use

https://github.com/nvm-sh/nvm#automatically-call-nvm-use

Exposing localhost to other networks

npx ngrok http 3000

Debugging in VSCode

Install nodemon globally with npm install -g nodemon.

Enable auto attach and run npm run dev in VSCode's integrated terminal.

Or in Debug window execute Launch nodemon (client-api) launch script.

Running tests in VSCode

Use Jest runner extension.