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

dotenvtypegen

v1.0.5

Published

Generate types for your .env files.

Downloads

2

Readme

dotenvtypegen

Generate types for your .env files.

Installation

// npm
npm install -D dotenvtypegen
// yarn
yarn add -D dotenvtypegen
// pnpm
pnpm add -D dotenvtypegen

Usage

CLI

npx dotenvtypegen [path_to_env] --save [path_to_output]

Module

import { Env } from "dotenvtypegen"

new Env("path/to/.env").save("path/to/output.d.ts")

Reference

CLI

| Option | Shortcut | Argument | Description | | ----------- | -------- | -------- | ----------------------------------------------------------- | | --namespace | -ns | string | Sets the namespace name for the generated type | | --interface | -in | string | Sets the interface name for the generated type | | --header | -hd | string | Adds the given string at the top of the generated type file | | --save | -sv | string | Where to save the generated file | | --optional | -op | bool | Will make all the type properties optional |

If multiple .env file paths are given the .env files will be merged.

Example

npx dotenvtypegen [path_to_first_env] [path_to_second_env] -ns MyNamespace -in MyInterface -hd "/* eslint-disable eslint/some-rule */" -op -sv type.d.ts

Module

class Env {
	private env: Record<string, unknown>

	/**
	 * @param path If multiple paths are given, the corresponding `.env` files will be merged.
	 */
	constructor(
		path: string | string[],
		private options: Config = {
			namespace: "NodeJS",
			interface: "ProcessEnv",
			header: "",
			optional: false,
		}
	) {}

	/**
	 * @returns The type file's content corresponding to the current instance.
	 */
	generate() {}

	/**
	 * Saves the types corresponding to the current instance to the given path.
	 */
	save(path) {}
}