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

@jonshort/cenv

v1.0.1

Published

Completely unnecessary port of cenv internals to node via. wasm

Downloads

22

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jonshortjonshort

Keywords

Readme

cenv-wasm

npm version

usage

Using a comment pattern in your .env files, easily swap between envs in local development.

Installation

Install globally via. npm

npm install -g @jonshort/cenv

Usage

  1. Add the "cenv" pattern to your .env file
VARIABLE_1=something

# ++ local ++
# API_ADDRESS=http://localhost:5000
# REQUIRE_LOGIN=false

# ++ live ++
# API_ADDRESS=https://myliveapi.com
# REQUIRE_LOGIN=true
  1. Run cenv, choosing an env keyword to use
cenv live
  1. Check your .env, the keyworded env vars will now be uncommented
VARIABLE_1=something

# ++ local ++
# API_ADDRESS=http://localhost:5000
# REQUIRE_LOGIN=false

# ++ live ++
API_ADDRESS=https://myliveapi.com
REQUIRE_LOGIN=true

Use via. npx

You can also run this cli via. npx which avoids having to install it globally, e.g:

npx @jonshort/cenv keyword

Uninstalling

  1. Check globally installed packages
npm ls -g
  1. Uninstall the package
npm uninstall -g @jonshort/cenv

Development

How to build the internals

  1. Install wasm-pack
cargo install wasm-pack
  1. Build with the target of nodejs
wasm-pack build --target nodejs
  1. Check the pkg/ folder - this is the compiled wasm
  2. Once built run node index.js and check everything is working as expected

How to publish the package

  1. Build the internals as above
  2. Remove the .gitignore file within the pkg/ folder
rm pkg/.gitignore

[!IMPORTANT] The above is extremely important - JS snippets won't be included otherwise 3. Do a dry-run publish and check the files are as expected

npm publish --dry-run
  1. Publish as normal
npm publish