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

browsertab

v0.0.3

Published

Track which tabs are visible and most-recently-used.

Downloads

17

Readme

BrowserTab

Building Javascript applications that run across multiple browser tabs can be tricky:

  1. Which browser tab is visible (if any)? You may want to do less work if you know that your current tab is not visible anyway.
  2. Which browser tab is primary? You may not want all tabs to process a server side event at the same time. For example, you would not want all of your tabs to generate a "new message" alert or sound.

BrowserTab encapsulates all of this behavior into a simple API:

  • BrowserTab.hidden() true when the current tab is hidden from the visitor
  • BrowserTab.primary() true when the current tab is the most-recently-used tab

Usage

In the browser, just include the module with <script src="browsertab.js"></script>. Then you should be able to use the global BrowserTab object:

if (BrowserTab.hidden()) {
  // This tab is not visible, maybe you can stop requesting data from the server
}

if (BrowserTab.primary()) {
  // This tab is primary, should be okay to trigger things like sounds from this one
}

You can also listen for changes to hidden/primary state:

BrowserTab.on("change:hidden", function() {
  // This tab changed from visible to hidden, or vice-versa.
});

BrowserTab.on("change:primary", function() {
  // This tab changed from primary to non-primary, or vice-versa.
});

Advanced Usage

You can use BrowserTab in node:

  1. Install the module using npm install browsertab
  2. At the top of your code, var BrowserTab = require("browsertab")
  3. Create a new BrowserTab object, for example: var tab = new BrowserTab({window: jsdom().createWindow()})

In general, you can inject all of the BrowserTab dependencies using the options:

var tab = new BrowserTab({
  window: window, // override window (helpful when mocking in unit tests)
  document: document, // override document (helpful when mocking in unit tests)
  localStorage: localStorage, // override localStorage (helpful when mocking in unit tests)
  storageNamespace: "_BrowserTabStorageNamespace" // change storage namespace for coordinating "primary" tab
})

Contributing

Found a bug? Have a new idea? Fork away and send us a pull request! Or call us, maybe?