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

@norjs/debug

v1.3.3

Published

Debug helpers for JavaScript

Downloads

15

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jhhjhh

Keywords

debugassert

Readme

@norjs/debug

Debug helpers for JavaScript.

Installation

You can install the module from the NPM: npm install -d @norjs/debug

Get current line number

You can use debug.__line to get current line number for debugging purposes.

Get current stack

debug.__stack is used by debug.__line to get the current line number.

Development or production mode tests

You can test for development and/or production mode (NODE_ENV) with the debug.isProduction() and debug.isDevelopment() which will return boolean values, true or false.

Start the app using NODE_ENV=production node app.js for production mode.

Start the app using NODE_ENV=development node app.js for development mode.

Default is development mode.

Write debug log messages

You may use debug.log(msg, [msg2...]) to write debug messages. This function will only write log if the app is running in the development mode. All non-string arguments will be converted to string.

Commercial Support

You can buy commercial support from Sendanor.