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

bad-line

v0.1.1

Published

Plugin for cute-stack that prints bad line for local source files

Downloads

47

Readme

bad-line

Plugin for cute-stack that prints bad line for local source files

NPM info

Build status dependencies devdependencies

Install and use

npm install --save bad-line

Include as a plugin for cute-stack

require('cute-stack')(require('bad-line'));

or do it in several steps

var cute = require('cute-stack');
cute.ui.badLine = require('bad-line');
cute('badLine');

Example

Let us initialize cute-stack in one file and then execute a file with an exception. You can see these files in the folder test

// demo.js
var cute = require('cute-stack');
cute.ui.badLine = require('bad-line');
cute('badLine');
require('./file-with-error');
// file-with-error.js
function bar() {
  throw new Error('This is an error!');
}
function foo() {
  bar();
}
foo();

This generates the following output, notice the actual source line contents

bad-line output

Compare this with standard output produced by pretty formatter for example

pretty output

bad-line prints the actual offending line, not just the function's name.

Small print

Author: Gleb Bahmutov © 2015 @bahmutov glebbahmutov.com

License: MIT - do anything with the code, but don't blame me if it does not work.

Spread the word: tweet, star on github, etc.

Support: if you find any problems with this module, email / tweet / open issue on Github