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 🙏

© 2025 – Pkg Stats / Ryan Hefner

static-console-plugin-dom-output

v1.0.0

Published

Plugin for printing your `static-console` messages to DOM.

Downloads

4

Readme

static-console-plugin-dom-output

Plugin for printing your static-console messages to DOM.

Gitter

Install

$ npm install --save static-console-plugin-dom-output

API

DomOutput

const c = require('static-console');
const DomOutput = require('static-console-plugin-dom-output');

document.addEventListener('readystatechange', () => {
    if (document.readyState == 'complete') {
        c.outputs.myLog = new DomOutput({
            rootNode: document.querySelector('main')
        });
        c.routers.std.tasks.set(c.outputs.myLog, c.models.raw);// We add task for StdRouter bundled with StaticConsole to convert messages with RawModel

        c.logt('info', `Starting log`);
    }
});

Test in any browser environment bundled with Node.js.

This code creates instance of DomOutput right after DOM is complete. c.outputs.myLog is now printing log to single element with tag name main.

Element main must contain something like <p class="message info">Starting log</p> as seen in inspector.

On line 9 we have added task to c.routers.std to convert messages with c.models.raw, and all of it is already bundled with StaticConsole.

By default static-console also has task to print with c.outputs.std. So you will have Starting log in your standard output too.

print(model)

model is the object that should have descriptive properties:

  • type - message type name. If it is falsy, then DomOutput.regularType will be used to mark message as regular.
  • data - string with message. It could be converted with RawModel.

rootNode

This option is required to print something. It should be that element, that is described as a "log".

messageTagName

Tag name that is used to create message node in DOM. Default: 'p';

messageAttributes

Object of attributes' names as keys and their values. String values will be parsed in such way:

  • contents in square brackets gonna be removed if message type is falsy, brackets themselves are removed,
  • $T will be replaced with message type name.

Default: { class: 'message[ $T]' }.

regularType

Type name that is used as fallback for falsy type (i.e. null value). Default: 'regular'.