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

screenlog

v0.3.0

Published

Bring console.log on the screen

Downloads

81

Readme

screenlog.js npm version

Bring console.log, on the screen


Ever faced a situation where you said "Why doesn't this bug show up when developer console is open!!"? And since the bug doesn't show when you have console open, you cannot do debug logging using console.log.

Enter screenlog.js. screenlog.js brings the developer console right on your screen so that you can do logging without having the developer console open always.

Example

Screenshot

Usage

Do npm install screenlog or bower install screenlog or download the project.

Drop dist/screenlog.min.js into your web application and initialize it with:

screenLog.init();

And you are done! By default, every next console.log (or info, warn and error) in your app now starts logging on the screen as well as the console. Or you can use screenLog.log() instead to just log on the screen.

Public API

screenLog.init([options])

Initializes the screen logger. It creates a customizable panel on the screen.

  • options - A map of additional options. _ logColor - Text color. Default is lightgreen. _ fontSize - Font size of logs. Default is 1em(Your browser's default). _ bgColor - Background color of the log panel. Default is black. _ releaseConsole - By default console.log is overridden to log on screen. You can avoid this behaviour by setting releaseConsole to true and instead use screenLog.log() API. Default is false.

screenLog.[log, warn, error, info](obj1 [, obj2, ..., objN])

Logs a message on the screen. Eg. screenLog.info('Info here').

  • obj1 ... objN - A list of JavaScript objects or strings to output. Just like console.log.

screenLog.clear()

Clears messages on the screen.

screenLog.destroy()

Removes the logger from the UI and reverts to original console functionality.

Browser Support

screenlog.js works best on latest versions of Google Chrome, Firefox and Safari.

Contributing

Interested in contributing features and fixes?

Read more on contributing.

Changelog

See the Changelog

License

Copyright (c) 2015-2017 Kushagra Gour, http://kushagragour.in Licensed under the MIT license.