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

@37bytes/prepare-environment

v2.0.0

Published

Utility to prepare the environment for a React application. Useful for CI.

Downloads

190

Readme

Usage

  1. prepare-environment ENV_NAME=stage In this case app looking for .environmentrc automatically. The file must be located in the root.

  2. prepare-environment ENV_NAME=stage CONFIG_PATH=configs/.environmentrc
    In this case app get .environmentrc file from the custom path.

Optional parameters default values

  • CONFIG_PATH = /,

Local developing

  1. create ./environments/.env.stage (env file must match ENV_NAME=stage)
  2. ts-node src/index.ts <...>
  3. npm run build&watch; node build/index.js <...>
  4. npm run build; chmod +x build/index.js; npm link; prepare-environment <...>
  5. example: ts-node src/index.ts CONFIG_PATH=__fixtures__/.environmentrc ENV_NAME=stage

version history

2.0.0

  • Elimination of allowedEnvironments. Instead, available environments are computed from the environments folder.
  • Added 'isEnvironmentExists' function in utils. The function takes parameters: targetEnvironment - the name of the environment, and pathToEnvironmentsFolder - the path to the folder containing the environments. The function checks for the presence of the .env.targetEnvironment file in the environments folder.
  • fix for environment name check

1.0.4

  • refactoring the script version

1.0.3

  • refactoring utils and main script

1.0.2

  • update .npmignore

1.0.1

  • fix small bugs

1.0.0

  • first version