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

debuggerjs

v1.0.18

Published

a small debugger for web in Native App

Downloads

9

Readme

debuggerjs

a small debugger for web in Native App

Why we need debuggerjs?

As we known, when developing something in App, we always can't get the error message if something wrong has happened. Meanwhile, if we have a tool showing the errors in the App web view, that would help us a lot to debug. So this is what I've done.

start

npm install debuggerjs

usage

var debug = require('debuggerjs'); 

or use es6

import debug from 'debuggerjs';
    

API

debug.init(options)

use debug.init(options) to listen all javascript code running error.

import debug from 'debuggerjs';
debug.init(options);

options

| key | value | default | | --- | --- | --- | | needShow | Boolean. Show errors on your device or not | true | | needReport | Boolean. Report errors to your server or not | false | | method | String. The way you send the error to server | 'post' | | url | String. The url you send the error to server | '' |

debuger.log(error)

or you can use debug.log() to log errors manually. The only param could be a Error object or a String.

var script = document.createElement('script');
    script.src = '/somethingBad.js';
    script.onerror = function (error) {
        debug.log(error);
        debug.log('write whatever you want to show');
    };
    
document.body.appendChild(script);