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

environment

v1.1.0

Published

Check which JavaScript environment your code is running in at runtime: browser, Node.js, Bun, etc

Downloads

24,075,530

Readme

environment

Check which JavaScript environment your code is running in at runtime

Install

npm install environment

Usage

import {isBrowser, isNode} from 'environment';

if (isBrowser) {
	console.log('Running in a browser!');
}

if (isNode) {
	console.log('Running in Node.js!');
}

[!NOTE] Runtime checks should be used sparingly. Prefer conditional package exports and imports whenever possible.

API

isBrowser

Check if the code is running in a web browser environment.

isNode

Check if the code is running in a Node.js environment.

isBun

Check if the code is running in a Bun environment.

isDeno

Check if the code is running in a Deno environment.

isElectron

Check if the code is running in an Electron environment.

isJsDom

Check if the code is running in a jsdom environment.

isWebWorker

Check if the code is running in a Web Worker environment, which could be either a dedicated worker, shared worker, or service worker.

isDedicatedWorker

Check if the code is running in a Dedicated Worker environment.

isSharedWorker

Check if the code is running in a Shared Worker environment.

isServiceWorker

Check if the code is running in a Service Worker environment.

isMacOs

Check if the code is running on macOS.

isWindows

Check if the code is running on Windows.

isLinux

Check if the code is running on Linux.

isIos

Check if the code is running on iOS.

isAndroid

Check if the code is running on Android.

Related

  • is-in-ci - Check if the process is running in a CI environment
  • is64bit - Check if the operating system CPU architecture is 64-bit or 32-bit
  • is - Type check values