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

dotenv-config-cli

v0.1.13

Published

A dot env config generator. Reads your .env file and generates a config file. Supports TypeScript and JavaScript.

Downloads

2

Readme

dotenv-config CLI

Test GitHub license

The dotenv-config CLI is a command-line tool that simplifies the process of generating a config file based on your .env file, supporting both TypeScript and JavaScript.

Installation

You can install dotenv-config globally using npm:

npm install -g dotenv-config

Usage

To use dotenv-config, run the following command:

dotenv-config generate
# There are the prompts you will see
? Specify the path to your .env file. The default location is the root directory ('.env'). › .env
? Specify the configuration file path. Default location is 'config/index.ts' or '.js' in the root directory. If specified, the file will be 'config.ts' or '.js' in the specified directory. › config
? Is this a TypeScript project? › (Y/n)

Note: When specifying the path to your configuration file, you have two options:

  1. If you do not provide a path, the configuration file will be located at 'config/index.ts' or '.js' in the root directory of your project.

  2. If you provide a path, the specified directory will be used, and the configuration file will be named 'config.ts' or '.js' within that specified directory.

This note provides additional clarification on how the configuration file path works based on your previous instruction.

The CLI will read your .env file and generate a config file with environment variables.

Example

After running the command, the CLI will generate a config in the root or in the folder you specified.

note:

PRIVATE_KEY=your_private_key_here
SEPOLIA_RPC_URL=https://example.com/rpc
COINMARKETCAP_API_KEY=your_api_key
ETHERSCAN_API_KEY=your_etherscan_api_key
export const envConfig = {
  PRIVATE_KEY: process.env.PRIVATE_KEY,
  SEPOLIA_RPC_URL: process.env.SEPOLIA_RPC_URL,
  COINMARKETCAP_API_KEY: process.env.COINMARKETCAP_API_KEY,
  ETHERSCAN_API_KEY: process.env.ETHERSCAN_API_KEY,
}

License

This project is licensed under the MIT License. See the LICENSE file for details.

Contributions

Contributions are welcome! If you have ideas for improvements or encounter issues, please open an issue or submit a pull request.

How to Contribute

  1. Fork the Repository: Click the "Fork" button on the GitHub page to create your copy of the project.

  2. Clone Your Fork: In your terminal, run the following command, replacing [your-username] with your GitHub username:

    git clone https://github.com/[your-username]/dotenv-config-generator.git
  3. Install Dependencies:

    npm install
  4. Make Changes: Create a new branch for your changes, make improvements or fixes, and commit your work:

    git checkout -b my-fix
    # or
    git switch -c my-fix
  5. Run the Project:

Run the following command to make sure the project is running properly:

dotenv-config generate
  1. Add Tests (if necessary) and Run Them:

    npm run test
  2. Push Your Changes to GitHub: Commit your changes and push them to GitHub. Then, open a pull request against the main branch.

    git add .
    git commit -m "Fix: Describe your fix or feature"

Links