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

dom-console

v5.1.1

Published

console.log output in the dom

Downloads

30

Readme

dom-console

console.log output in the dom

description

very convenient when experimenting with npm libraries in the browser. For example using requirebin.com

By default.it adds a console DOM element to the bottom of the page, which can be cleared and minimized/maximized via buttons and shows everything that can otherwise be seen in the DevTools JavaScript console.

example

see http://serapath.github.io/dom-console

usage

var Buffer = require('buffer').Buffer
var domconsole = require('dom-console')
var opts = { lineLength: 60 } // default
var api = /*element*/ domconsole(/*opts*/).api

console.log(new Buffer(5))

var x = { leaf: 'leaf' }
x['circular1'] = x
x.y = {}
x.y.circular2 = x.y
console.log(x)

console.log({a:'x', fn:function(x){return 5}})
console.log(new Date)
console.log({a:'b',c:[1,2,3],x:{y:{z:['a',{b:'c'}]}}})
console.log(null)
console.log(undefined)
console.log("hey")
console.log(false)
console.log(true)
console.log(function asdf () {})
console.log(12)
console.log(/asdf/)
console.log((function(){ return arguments })(1,true))
console.log([])
console.log(document.createElement('div'))
console.log(NaN)

console.log({a: '5'})
console.error({a: '5'})
console.log(document.createElement('div'))
console.error(document.createElement('div'))
var div = document.createElement('div')
div.innerHTML = '<div><div>asdf</div></div>'
console.log(div)
console.log('WWWWWWWWWW WWWWWWWWWW WWWWWWWWWW WWWWWWWWWW WWWWWWWWWW WWWWWWWWWW WWWWWWWWWW WWWWWWWWWW ')

console.info('it works :-)')

// api usage
api.toggle() // expand or minimize the dom-console
console.log(api.serialize()) // retrieve the log that was logged to the dom-console
api.clear() // clear the content of the dom-console

api.log('visible in devtools console & only this dom-console instance')
api.info('visible in devtools console & only this dom-console instance')
api.error('visible in devtools console & only this dom-console instance')

// also logs errors nicely
function test (p) { var x = JSON.parse(p) }
test(function(){})

console.log(new Error('Ups! Something wrong...'))
console.error(new Error('Ups! Something wrong...'))