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

env2config

v1.0.1

Published

A simple utility to parse your env for better autocomplete

Downloads

3

Readme

env2config

env2config is a handy npm package that reads environment variables from your project's .env file and generates a JavaScript configuration file (Typescript support soon!). This helps with better autocomplete and type safety when working with environment variables in your Node.js project.

Installation

You can use the handy npx command. No need to install any dependancy 😁

To generate the configuration file, simply run the following command in your project's root directory:

npx env2config

This will create a env.config.js file inside src/config. The generated file will export an object containing all the key-value pairs from your .env file, allowing you to import and use with autocomplete.

// env.config.js
export const envConfig = {
  NODE_ENV: process.env.NODE_ENV,
  PORT: process.env.PORT,
  DATABASE_URL: process.env.DATABASE_URL,
};

module.exports = envConfig;

You can then import this envConfig object in your application and use it like any other module:

import { envConfig } from "./config/env.config.js";

console.log(`Running in ${envConfig.NODE_ENV} environment`);
console.log(`Listening on port ${envConfig.PORT}`);

Configuration

By default, env2config looks for a .env file in the root directory. If your .env file has a different name or is located elsewhere, you can specify its path using the --env-file option:

npx env2config --env-file=/path/to/my/.env.prod

You can also customize the output file name and location using the --output option:

npx env2config --output=src/config/env.config.js

You can choose to exclude certain entries using --exclude-prefixes option:

npx env2config --exclude-prefixes="['SECRET_']"

Contributing

Contributions are welcome! Please open an issue or submit a pull request on the GitHub repository.

License

This project is licensed under the MIT License.