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

rollup-plugin-dotenv

v0.5.1

Published

Rollup plugin that loads available .env files and replaces the defined variables with their values

Downloads

41,314

Readme

rollup-plugin-dotenv

Installation

npm install rollup-plugin-dotenv

Usage

Create a rollup.config.js configuration file and import the plugin:

import dotenv from "rollup-plugin-dotenv"

export default {
  input: "src/index.js",
  output: [
    dir: "dist/build"
  ],
  plugins: [
    dotenv()
  ]
}

create your .env file in the root of your project.

# .env
FOO=bar

so you can use FOO in your javascript files.

// src/index.js
console.log(process.env.FOO)

your env variables will be replaced by their values in your bundled file.

// dist/build/index.js
console.log('bar')

if you want to know more about the principle and restrictions of replacement, please read @rollup/plugin-replace notes.

Options

You can specify the options below.

cwd

Type: String Default: "."

directory in which to search for env files.

envKey

Type: String Default: "NODE_ENV"

key used to search for .env files by node environment

Rollup will merge env vars located at

[
  `.env.${process.env[envKey]}.local`,
  `.env.${process.env[envKey]}`,
  '.env.local',
  '.env',
]

so if you are in prod, rollup will search in

['.env.prod.local', '.env.prod', '.env.local', '.env']

and merge the result.

LICENSE (MIT)