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

console-board

v0.0.7

Published

Display all console output in real html

Downloads

9

Readme

console-board

Display all console output in real html

Check the demo

Introduction

Install

npm i console-board --save-dev

Usage

import { injectRender } from 'console-board'; And Inject somewhere it at your root component {injectRender()} Then the component will be used in development and the console will be patched

Or

You could use import { LogList } from 'console-board' as you want

Exports

LogList the main component which does the patch and displaying all together

  • toggleByTouch default false: Instead of showing the 😂 button, tap three times in a row to display the log pannel
  • showOnInit default false: show log pannel on start
  • showInput default false: show an input that eval the code (type clear to clear the console board)
  • persistentKey default @@console: [TODO] set the key to store the output, set it to null to disable persistence

patchConsole proxy the console and call your custom function before every console call Return a proxied console. Used internally in LogList.

injectRender Helper function to render the LogList only on development

Why

Sometimes the developer console is not available to use, and logging becoming tedious. And some logging options provide plain text output which is not joyful to work with.

Use cases

  • When the page is in a webview where no remote debugging is available
  • When developing React Native apps and turning on remote debugging is too slow
  • When you are tired of the default console output

TODO

  • [x] Proxy console on Chrome and Safari
  • [x] Maintain states
  • [x] React component
  • [x] Accurate output for complex structure
  • [x] Interactive
  • [ ] Persistence
  • [ ] React Native component
  • [ ] Plain JS component