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

esbuild-plugin-env

v1.1.1

Published

ESbuild plugin that setup environment variables using dotenv

Downloads

2,120

Readme

esbuild-plugin-env

ESBuild plugin that use dotenv to setup environment variables

Installation

npm install esbuild-plugin-env --save-dev
pnpm install esbuild-plugin-env --save-dev
yarn add esbuild-plugin-env --save-dev

Environment

  • process.env.NODE_ENV: use minify to know whether the app will be set to production.
  • process.env.PROD: {boolean} whether the app is running in production.
  • process.env.DEV: {boolean} whether the app is running in development (always the opposite of import.meta.env.PROD)
  • process.env.ESB_*: key format that will be fetch in environment variables

Optional Parameters

  • isProd: overwrite the NODE_ENV to set to production
  • startkey: overwrite the starting key that the app will set, default is ESB

Usage in script

import esbuild from "esbuild"
import env from "esbuild-plugin-env"

// minify to true to make the NODE_ENV in production
esbuild.build({
  entryPoints: ["./src/index.js"],
  bundle: true,
  minify: true,
  outfile: "./dist/index.js",
  plugins: [env()],
})

Using Custom Directory

import esbuild from "esbuild"
import env from "esbuild-plugin-env"

esbuild.build({
  entryPoints: ["./src/index.js"],
  bundle: true,
  minify: true,
  outfile: "./dist/index.js",
  plugins: [
    env({
      isProd: true
      startKey: "ESB"
    }),
  ],
})