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

runtime-info

v1.0.1

Published

Isomorphic, nano-sized library to check where your code is running: isServer(), isBrowser(), isWebWorker()

Downloads

32

Readme

Nano untility library for JavaScript runtime detection

This is important for SSR/SSG, isomorphic runtime code checks: Should certain code be executed or not? Some code works only on server, some code works in browser, and some in browser, but not in WebWorkers.

Instead of a weak if (typeof window !== 'undefined') { ... } etc. checks which are easy to mistaken you can use this safe, fast and nano sized library. Using it gives you more readble code and reliability.

  • ✅ JavaScript runtime checks: isBrowser(), isServer(), isWebWorker()
  • ✅ Just 174 byte nano sized (ESM, gizpped)
  • ✅ Tree-shakable, side-effect free, so maybe just 58 byte for you
  • ✅ Zero dependencies
  • ✅ First class TypeScript support
  • ✅ 100% Unit Test coverage
  • yarn: yarn add runtime-info
  • npm: npm install runtime-info
import { isBrowser, isServer, isWebWorker } from 'runtime-info'

if (isBrowser()) {
  // safely use window, location, etc. here
}

if (isServer()) {
  // safely use Node.js/Deno API's here like process
}

if (isWebWorker()) {
  // safely use postMessage() inside of a webworker
}
const { isBrowser, isServer, isWebWorker } = require('runtime-info')

// same API like ESM variant

If you're running inside of a server-side environment where globals like window and document are defined (JSDOM), then you're effectively running in a browser-compatible environment, and this library will return true for isBrowser and false for isServer. This is an edge case. You can check for this using the following code: navigator.userAgent.includes("jsdom")