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

@taktikal/env

v1.1.1

Published

Utility for dynamic runtime environment variables in compiled Server Side Rendered apps.

Downloads

2

Readme

@taktikal/env

Utility for dynamic runtime environment variables in compiled Server Side Rendered apps.

Getting started

Configuration

Create enums for PrivateEnv and a PublicEnv.

// types.ts
export enum PrivateEnv {
  API_URL = "API_URL",
}

export enum PublicEnv {
  SENTRY_DSN = "SENTRY_DSN",
}

Register the environment on the server side. This example is for Next.js

// _document.tsx
import { registerEnv } from "@taktikal/env";
import { PublicEnv, PrivateEnv } from "~/types";

const envScript = registerEnv({ public: PublicEnv, private: PrivateEnv }, {
  API_URL: "This is private",
  SENTRY_ENV: "This is public",
  PRIV: "priv",
});

// ...

<script dangerouslySetInnerHTML={{ __html: envScript }} />,

The string returned from registerEnv will be in the form __ENV__={ ...publicEnv }. The serialized __ENV__ object is html safe.

Then we create getters for both publicEnv and privateEnv with createEnvGetters.

// utils/env.ts
import { createEnvGetters } from "@taktikal/env";
import { PublicEnv, PrivateEnv } from "~/types";

export const { getPrivateEnv, getPublicEnv } = createEnvGetters({
  public: PublicEnv,
  private: PrivateEnv,
});

Usage

getPrivateEnv has access to both the public and private env.

// Server side
import { getPrivateEnv } from "~/utils/env";

const apiUrl    = getPrivateEnv("API_URL");    // Getting from private env
const sentryDsn = getPrivateEnv("SENTRY_DSN"); // Getting from public env

getPrivateEnv("INVALID_KEY"); // Error: Key 'INVALID_KEY' does not exist in private or public env.

getPublicEnv only has access to the public env.

// Client side
import { getPublicEnv } from "~/utils/env";

const sentryDsn = getPublicEnv("SENTRY_DSN"); // Getting from public env

getPublicEnv("API_URL"); // Error: Key 'API_URL' does not exist in public env.