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

rnenv

v1.0.0

Published

React Native JS only environment variable

Downloads

2

Readme

RNENV

React Native JS-only environment variable

Credits

This project is a fork of cross-env and envfile

Goals

The goals of this project is to create an environment variable library in react native that can be installed as dev dependency. and Javascript only. the environment variable can not be used in the native realm of the project.

How to init env folder

you can init yourself by adding this structure in the root of your app

env
- - development.env
- - production.env
- - index.js

you can add as many as env_name.env that you like, but you should also add the index.js file.

or if you use yarn you can run yarn run rnenv-init

or add this command in your scripts section in package.json: "rnenv-init": "rnenv-init"; then run npm run rnenv-init;

ENV Format

after you init the env folder you can write in your env_name.env like a standard envfile for example in development.env:

BASE_URL=localhost:8000

then in production.env:

BASE_URL=htttp://production.example.com

How to parse the env file

The idea is like the one used in cross-env. so you run rnenv ENV=envname then followed by the command. for example if you wan to run android with dev env and then build using production env you would add those in your scripts in package.json:

    "android:prod": "rnenv ENV=production cd ./android && ./gradlew assembleRelease",
    "android:dev": "rnenv ENV=development react-native run-android",
    "start:dev": "rnenv ENV=development npm run start",

each time rnenv run, it will change the content of index.js in your env folder according to the env you selected

How to use the env file

finally in your file you can import the env/index.js for example

import ENV from "./env";

function HelloEnv() {
  return (
    <View>
      <Text>Current api URL = {ENV.BASE_URL}</Text>
    </View>
  );
}