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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ledgerhq/live-env

v3.0.0

Published

Ledger Live environment definition

Readme

live-env

[!NOTE] Status: STABLE — Production-ready; API is considered stable.

@ledgerhq/live-env is the framework for typed runtime environment variables, enabling interoperability across @ledgerhq/* libraries. It exposes a reactive API (getEnv, setEnv, changes) but ships no env-var definitions — those live in the workspace-private @shared/env layer inside the monorepo.

What it does

  • Provides getEnv(key) / setEnv(key, value) for safe, typed access
  • Emits a reactive stream (changes) when a value changes, enabling subscriptions
  • Supports parsing from raw strings (e.g. process.env) with int/float/bool/JSON parsers
  • Enforces initialization: every API throws until injectDefinitions() has been called

Key exports / concepts

  • injectDefinitions(defs) — must be called once before any other API, with a record of EnvDef entries
  • getEnv(name) — read the current value of an env key
  • setEnv(name, value) — override a value at runtime
  • setEnvUnsafe(name, rawString) — parse and set from a raw string (e.g. process.env)
  • changes — observable of { name, value, oldValue } for reactive env updates

Usage inside the ledger-live monorepo

Internal packages import from @shared/env, which calls injectDefinitions() at module load and re-exports a fully typed API. You do not need to call injectDefinitions() yourself.

import { getEnv, setEnv, changes } from "@shared/env";

const timeout = getEnv("GET_CALLS_TIMEOUT"); // number
const swapUrl = getEnv("SWAP_API_BASE"); // string
changes.subscribe(({ name, value }) => console.log(name, value));

Usage outside the ledger-live monorepo

External consumers must supply their own definitions and call injectDefinitions() before any getEnv/setEnv call. The API will throw if called before initialization.

import {
  injectDefinitions,
  getEnv,
  setEnv,
  changes,
  intParser,
  boolParser,
  stringParser,
} from "@ledgerhq/live-env";

// 1. Define your env vars
const myDefinitions = {
  MY_TIMEOUT: {
    def: 30_000,
    parser: intParser,
    desc: "Request timeout in ms",
  },
  MY_DEBUG: {
    def: false,
    parser: boolParser,
    desc: "Enable debug logging",
  },
  MY_API_URL: {
    def: "https://api.example.com",
    parser: stringParser,
    desc: "Base API URL",
  },
} as const;

// 2. Inject once at app startup, before any imports that call getEnv
injectDefinitions(myDefinitions);

// 3. Use the API
const timeout = getEnv("MY_TIMEOUT"); // unknown at framework level — cast as needed
setEnv("MY_DEBUG", true);
changes.subscribe(({ name, value }) => console.log(`${name} changed to`, value));

[!IMPORTANT] injectDefinitions() must be called before any module that calls getEnv or setEnv is evaluated. Place it at the very top of your application entry point, before other imports that may trigger env reads.