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

enchanted-debug

v1.0.0

Published

a wrapper around the amazing debug that automaticly adds namespace based on the path and project root.

Downloads

2

Readme

#enchanted-debug

Coverage Status Dependency Status Codeship Status for SindreSvendby/enchanted-debug

a wrapper around the amazing debug package that automaticly adds namespace based on the path and project root.

This module will be obsolete when debug is in version 3, sjekk out this github issue for progress on that

Cons

Performance is not the best, since we use callsite. So keep that in mind.

Pros

  1. Do not need to

Prerequisite

enchanted-debug is a peerDependecy of debug and you can need to specified this your self

So install debug

yarn add debug / npm install --save-exact debug

Installation

yarn add enchanted-debug or npm install --save-exact enchanted-debug

Usage

// assume this  file is under <project-root>/src/services/fetch/index.js
import eDebug from 'enchanted-debug'
// project root folder name, for this project
const { log, error } from eDebug('<project-root>')

log('starting')
error('failed')
log('finished')

Output from debug module will be

// output will be:
<project-root>:src:services:fetch starting
<project-root>:error:src:services:fetch: failed
<project-root>:src:services:fetch finished

This would be the same as doing this with plain debug:

import debug from 'debug';

const path =  '<project-root>:<subfolder>:<subfolder>:<subfolder>:<filename-without-ending>'
const subpath ='<subfolder>:<subfolder>:<subfolder>:<filename-without-ending>'
const log = debug(`${path}`);
const error = debug(`<project-root>:error:<project-path>`);

// use error or log, to log with the module
log('starting')
error('failed')
log('finished')

Good to know

Skip filename ending:

enchanted-debug/src/services/fetch/utils.js =>  enchanted-debug:src:services:fetch:utils

Skip index as last part

enchanted-debug/src/services/fetch/index.js =>  enchanted-debug:src:services:fetch

Failure

if (typeof callstack.length === 'number' && callstack.length > 1) if the above line for some reasons fails, the logging will be done under

Dependencies

only have callsite as a dependency

Credits

Created by the developers in Aller Media