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

@wider/utils_where-am-i

v1.1.22

Published

Determine where your code is running

Downloads

41

Readme

@wider/utils_where-am-i YDR Utilities - Where am I?

Introduction

Disclose where your code is running

A javascript tool that investigates and reports on the environment in which it is running. Presently coded for nodejs, browsers and various windows environments such as WScript or ASPclassic. It will report "unknown" for environments that the author does not have access tp test.

There are no dependencies.

Documentation

Full Documentation

Install

npm install "@wider/utils_where-am-i"

Use

// from ES MOdule
import { genre, os, engine, version, _genres } from "@wider/utils_where-am-i/index.js";

// from commonJS  module
const  { genre, os, engine, version, _genres } = require ("@wider/utils_where-am-i");

// from non-module environments 
yourLinkOrImportMethod("a/path/to/@wider/utils_where-am-i/index.js)
var where = whereAmI();

The code in this package has been written deliberately in an early dialect of javascript so that identical code can run on legacy environments by just loading the file ./index.js which then exposes the whereAmI() method. This generates a simple object with the same properties that are exported in the node environment.

See the Example for the earliest versions of supported environments.

Documentation and Example Results

On npm, you can run this in RunKit and see the details for the linux server that runs npm. Typically that will return

{
    _genres: /unknown|server|browser|script/,
    genre: "server",
    engine: "node",
    version: "v14.17.4",
    computerName: "YDR-HP-2015"
    os: "linux"
}

Developer documentation and examples are available at the @wider website