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

condsole

v0.9.0

Published

Only log to the console if you're looking at it! [Huge perf wins!](https://stackoverflow.com/a/26754011)

Downloads

5

Readme

condsole: conditional console

Only log to the console if you're looking at it! Huge perf wins!

  • By default, only executes console methods if devtools window is open
  • Can pass conditions to evaluate to execute console methods in node.js / browser environments
  • All methods available to console are available to condsole

Recommended usage

// ./utils/console.js
import condsole from 'condsole'

const options = {
  browser: true,
  node: true,
  devtools: true,
}

export default condsole(options)
// ./main.js
import condsole from './utils/console'
// or, if you prefer destructuring: 
// import { log, warn, error } from './utils/console'

// then, use condsole like you would `console`
condsole.log('Hello world', { foo: 'bar' }) 
// given the default options, this would have only written to console
// if devtools were open at the time condsole was initialized

Options

browser (boolean): default true

  • When false, forces all console calls to be no-ops in a browser environment
  • Example: set browser: !!localStorage.getItem('debug') to only write to console if the debug localStorage key exists

node (boolean): default true

  • When false, forces all console calls to be no-ops in a node.js environment

devtools (boolean): default true

  • When false, writes to console regardless if devtools is open or not
  • Note: Only checks if devtools is open once (when condsole is instantiated). If you instantiate condsole during page load, it will check if devtools is open at that moment, and determine whether to write to console based on that.