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 🙏

© 2025 – Pkg Stats / Ryan Hefner

url-env

v4.0.4

Published

Select an environment by url

Downloads

11

Readme

url-env

Select an environment by url

Install

pnpm install url-env
npm install url-env

Features

  • ✅ TypeScript support with full type definitions
  • ✅ ES Modules and CommonJS support
  • ✅ UMD build for browser usage
  • ✅ Zero dependencies
  • ✅ Works in Node.js and browsers
  • ✅ Comprehensive test suite with 100% coverage
  • ✅ Automated CI/CD with GitHub Actions
  • ✅ Trusted publishing to npm

Usage

Make sure you include polyfills for Object.prototype.entries and String.prototype.startsWith if you need this to work with older browsers.

Basic Usage (JavaScript)

import { fromObject } from 'url-env';

// Or using CommonJS
// const { fromObject } = require('url-env');

const availableEvironments = {
  'https://localhost:9300': 'local',
  'https://dev.mydomain.com': 'dev',
  'https://test.mydomain.com': 'test',
  'https://mydomain.com': 'prod'
};

const {pair, url, env} = fromObject(availableEvironments);

// When window.location.href starts with https://dev.mydomain.com
console.log(pair); // ['https://dev.mydomain.com', 'dev']
console.log(url); // 'https://dev.mydomain.com'
console.log(env); // 'dev'

TypeScript Usage with Environment Objects

import { fromObject, EnvObject } from 'url-env';

// Define your environment configuration type
interface EnvironmentConfig {
  name: string;
  apiUrl: string;
  local: boolean;
  debug?: boolean;
}

const environments = {
  'https://localhost:8100': {
    name: 'development',
    apiUrl: 'http://localhost:3000/api',
    local: true,
    debug: true
  },
  'https://staging.mydomain.com': {
    name: 'staging',
    apiUrl: 'https://api-staging.mydomain.com',
    local: false,
    debug: true
  },
  'https://mydomain.com': {
    name: 'production',
    apiUrl: 'https://api.mydomain.com',
    local: false,
    debug: false
  }
};

// TypeScript automatically infers the type from your configuration
const result: EnvObject<EnvironmentConfig> = fromObject(environments);

console.log(result.env.name);    // Type-safe access to 'name'
console.log(result.env.local);   // Type-safe boolean
console.log(result.env.apiUrl);  // Type-safe string

// Example: Configure your app based on environment
if (result.env.local) {
  console.log('Running in local development mode');
  // Enable hot reloading, detailed logging, etc.
} else {
  console.log(`Running in ${result.env.name} mode`);
}

Custom URL Matching

// Using strings other than window.location.href (useful for testing)
const {pair, url, env} = fromObject(availableEvironments, 'https://staging.mydomain.com/some/path');

Cutting a release (it is crucial for CI to be on latest npm for trusted publishing)

  • Put in as many pull requests into main
  • Switch to main locally and pull it down to make sure it is fresh
  • Run npm run release:patch (or minor/major) which will make a tag
  • Manually create GitHub release from the new tag from the last step
  • GitHub Actions will auto-publish