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-filter-js

v0.2.0

Published

Make native console.log() (and other console methods) proxied and filtered by text string

Downloads

10

Readme

consoleFilter.js

Make native console.log() (and other console methods) proxied and filtered by text string

Use

Include file consoleFilter.js into document. After this script everything in console will be blocked. For filtering place variable:

const consoleFilter = {
	allowlist: [ 'items' ],
	blocklist: [ 'word', 'another', 'word' ],
};

before including consoleFilter.js into document. And in your logs use format with some identifier into beginig. Like class name or script name. It will be easy to filter that. So from example 'items' can also be file name 'myNewScript.js' or class name 'MyWorker' or anything. It can be presented once or multiple times.

including should look like:

<script src="path/to/consoleFilter.js" crossorigin="anonymous" integrity="sha256-uXXs7C2BDEgOxzU68GoX2snxzRxizF6dVw1sdR3rcpw="></script>

a simple example of usage is in the example-usage.html file


And your console logs (debugs, …) should look like console.log( 'myNewScript.js simple console.log()' );. Lot of examples in file example-usage.html.

If you not present variable consoleFilter in a global scope so all console commands will be filtered (blocked).

Also not both allowlist and blocklist are needed. If you need only allow some classNames (file names, identifiers, whatever, …) it could look like:


Services

Unpkg: https://unpkg.com/console-filter-js

NPM: https://www.npmjs.com/package/console-filter-js

Licence

CC BY-SA 4.0

This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/ or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042, USA.


More info at https://iiic.dev/console-filter-js