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

lazydebugger

v0.5.1

Published

Dead simple, Node.js based logging utility.

Downloads

5

Readme

lazydebugger

:zzz: Dead simple, Node.js based logging utility.

Build Status npm version License: MIT PRs Welcome

NOTE: THIS MODULE IS CURRENTLY IN BETA

Description: Create a logger for your project the lazy way. Using a single YAML file called debugger.yml, configure your settings, then create your log objects in the same file and access them through the API.

Installation

$ npm install lazydebugger

Usage

Note: If you don't have a file named debugger.yml in the root directory of your project, this module won't work! This will change in the 1.0 release to support multiple filenames and formats. For now, name your debugger file exclusively debugger.yml and check out this quick yaml cheatsheet if you don't already know YAML syntax.

Step 1: You need to configure your debug settings. Here is an example of all the allowed options.

# debugger.yml

settings:
  debug: true
  output:
    file: true
    path: "./log"
    filename: test.log
    console: true
    color: red
    bold: true

Step 2: Create your log objects in the same file.

# debugger.yml

settings:
  debug: true
  output:
    file: true
    path: "./log"
    filename: test.log
    console: true
    color: red
    bold: true

0:
  type: pass
  prefix: Success
  message: valid log object detected
1:
  type: fail
  prefix: Error
  message: invalid log object detected
2:
  type: pass
  prefix: Success
  message: some other success message

Step 3: Use the module. Provide the main method a log id and lazydebugger will print that log id's message to a file and the console respective of your settings.

/* example.js */

const log = require('lazydebugger');

if(userInputIsValid) {
  log(0);
}
else {
  log(1);
}

Step 4: View your logs! The output path and filename are set in the settings object of the debugger.yml file. If you set console: true in the settings object, you should have your output in the console as well.

- /root
    - debugger.yml
    - example.js
    - /log
      - test.log

License

MIT License

Copyright (c) 2019 Michael Arakilian

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.