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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cronosmain/env

v1.5.1

Published

Sets variables from the .env file. Allows to get them safely.

Readme

env

Description

Sets variables from the .env file. Allows to get them safely.

How to install?

npm install @cronosmain/env # or any other package manager

What is it for?

I have forgotten countless times to specify the environment variable when running an application.

Usually nodejs does not react if process.env has no value by key and proudly returns undefined. Often such silly errors are hard to catch and understand why the application crashes after all. Often the error logs don't give any specifics about what happened. This simple library solves that problem.

.env file

The first time you import from this library, a side effect is performed. It will find the .env file in your current working directory and install the variables from there. If the file doesn't exist (e.g., in a production run), it won't do anything.

Examples of .env file syntax:

# Values must be set in double quotes, not single quotes.
VAR1 = "value"
VAR2="value"
VAR3 ="value" # comment
# VAR4 ="value" | will not be set because it is a comment

How to use?

import { app } from './app.ts'
import env from '@cronosmain/env'
// env() can be imported as default:
// import env from '@cronosmain/env'
// or as a named variable:
// import { env } from '@cronosmain/env'

// If var is defined, the value will be returned
// Otherwise Error-like object will be thrown
app.listen(env('TCP_PORT'), () => console.log('Listening...'))

// You can pass the fallback as a second argument
let URL = env('SERVICE_URL', 'https://example.com')