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

@u-rogel/slick-console

v0.0.2

Published

``` # npm npm i @u-rogel/slick-console

Downloads

3

Readme

Install

# npm
npm i @u-rogel/slick-console

# yarn
yarn add @u-rogel/slick-console

Usage

At your root file require and call it

// ./src/index.js
require('@u-rogel/slick-console')()

console.log('test log')

// 3/2/2023 2:00:00 PM src/index.js:3:9

Configs

| prop | type | default | description | | - | - | - | - | | relativeDepth | number | 1 | Call stack depth. If used inside logger utils increase to see where the logger function was called | consoleColors | object | {} | The default console colors |

consoleColors accepts those optional props: default, time, position, log, info, warn, error, success. Each one is a string of node.js console color. Look on the default bellow for example.

By default the colors will be:

const DEFAULT_CONSOLE = '\x1b[0m' // reset
const DEFAULT_TIME = '\x1b[34m' // blue
const DEFAULT_POSITION = '\x1b[35m' // magenta
const DEFAULT_LOG = '\x1b[0m' // reset
const DEFAULT_INFO = '\x1b[36m' // cyan
const DEFAULT_WARN = '\x1b[33m' // yellow
const DEFAULT_ERROR = '\x1b[31m' // red
const DEFAULT_SUCCESS = '\x1b[32m' // green

Check this gist for more console codes

Road Map

  1. Log level printed out
  2. Config what part of the enhancers you would like to see
  3. Return a console instance that will not override the global console
  4. Allow configuration change for single log call