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

is-where

v1.0.2

Published

JS environment check functions like `isWebkit() isSafari() isBrowser() isNode()` etc. A simple & small integration.

Downloads

1,245

Readme

is Where? 🙈

Very simple & small JS environment check functions.

npm i is-where

Also check out is-what 🙉

Motivation

I built is-where because I kept Stack Overflowing the same things for every project.

I was looking for:

  • A simple way to check which environment (Node, Browser, Deno, ...)
  • A simple way to check for which browser (WebKit, Safari, Chrome, Firefox, ...)
  • Functions that don't crash when executed in any environment
  • 0 dependencies

Usage

is-where is really easy to use, and most functions work just like you'd expect.

// import functions you want to use like so:
import { isBrowser, isNode, isWebKit } from 'is-where'
isBrowser() // true / false
isNode() // true / false
isWebKit() // true / false

List of functions

Environments

  • isNode()
  • isBrowser()
  • isWebWorker()
  • isJsDom()
  • isDeno()

Browsers

  • isWebKit()
  • isSafari()

Meet the family (more tiny utils with TS support)

Source code

See the full source code here.