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

quanto-commons

v1.0.50

Published

Quanto Common Tools

Downloads

104

Readme

  ____            _         ___                    _
 / ___|___  _ __ | |_ __ _ / _ \ _   _  __ _ _ __ | |_ ___
| |   / _ \| '_ \| __/ _` | | | | | | |/ _` | '_ \| __/ _ \
| |__| (_) | | | | || (_| | |_| | |_| | (_| | | | | || (_) |
 \____\___/|_| |_|\__\__,_|\__\_\\__,_|\__,_|_| |_|\__\___/

Welcome to the Quanto Commons repository! These are tools / constants / models that are shared among our projects. Feel free to contribute / make it better.

QuantoColors

QuantoColors uses the node-colors package and makes a standard color display over our applications. To use it just import QuantoColors from quanto-commons and run it:

import { QuantoColors } from 'quanto-commons';

QuantoColors();

Then you should be able to use like this in any string:

const myRainbowString = 'This is my rainbow string'.rainbow;
console.log(myRainbowString);

should output:

Rainbow String

The current usable color set is:

  • silly => rainbow
  • input => grey
  • verbose => cyan
  • prompt => grey
  • info => green
  • data => grey
  • help => cyan
  • warn => yellow
  • debug => blue
  • error => red

printQuantoHeader

This call is used to print out headers like this:

Rainbow String

To use it's very simple.

import { printQuantoHeader } from 'quanto-commons';

printQuantoHeader('Quanto Commons', 'Test');

The second parameter is optional and denotes the second line.

ErrorObject / ErrorCodes

The ErrorObject model is used across our applications to denote an error when returning or throwing an exception. It has five fields:

  • errorCode => A string from ErrorCodes
  • stackTrace => An optional string containing the stacktrace
  • errorField => An optional string containing the field related to the error
  • message => A brief message saying why the error ocurred
  • errorDat => An optional object that can contain extra data related to the error

The ErrorCodes is a type of enum that contains a map from a standard errorCode string to a good name to be used on ErrorObject (or other places).

Fatal "Clip" Exception Message

For the most waited feature of quanto-commons, here it is. Your master helper for fatal exceptions:

Rainbow String

Just use:

import { boxMessage, bclipError } from 'quanto-commons';
const myFatalHelperMessage = boxMessage(bclipError(new Error('Fatal Exception Test')));
console.log(myFatalHelperMessage);

Have fun!