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

dysf.utils

v0.1.2

Published

Custom dysfunctional utilities for node.js

Downloads

9

Readme

Table of Contents generated with DocToc

dysf.utils Build Status

Custom dysfunctional utilities for node.js !!!

Usage

  • utils - utils = require("dysf.utils").utils;
  • logger - logger = require("dysf.utils").logger;
  • mock - mock = require("dysf.utils").mock;

API

logger

A key reason for creating my own logger was to print file path and line numbers from where a log message was called. Additionally it prints the date/time and also has a few additional levels of logging.

  • logger.setLogLevel( id )
    • 0: system, 1: error, 2: warn, 3: event, 4: info, 5: debug, 6: trace. Default is 4 (info)
  • logger.system ( msg | obj )
    • Useful for system level notifications.
  • logger.error ( msg | obj )
  • logger.warn ( msg | obj )
  • logger.event ( msg | obj )
    • Recommended for key events like new tranactions / sessions / requests etc.
  • logger.info ( msg | obj )
    • Recommended for notable phases within a transaction like handlers, methods etc.
  • logger.debug ( msg | obj )
    • Recommended for useful property values or callback tracking.
  • logger.trace ( msg | obj )
    • Recommended for detailed debugging like printing object contents.

utils

A random utility collection of one. Render a file to the Response in cases where you are not using a micro or mega framework.

  • utils.renderFile ( response, path, replaceParams, callback )
    • response: Http Response
    • path: path to file
    • replaceParams: A hash of Ket Value pairs with the key representing the string to replace with the Value.
    • callback: to help with callback hell.

mock

The start of a few mock objects primarily useful in quick and dirty unit testing.

  • mock.response ( text )

Installation

Global

  • Run: sudo npm install dysf.utils -g
  • Usually installed at - /usr/local/lib/node_modules/dysf.utils

Project

  • Add "dysf.utils": "x.x.x" to the dependencies section of your project's package.json
    • Example "dependencies": { "dysf.utils": "x.x.x" }
  • Run npm install in the director with your package.json
  • Usually installed at - PROJECT_DIR/node_modules/dysf.utils