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

realm-env

v1.0.19

Published

[Realm Env](https://www.npmjs.com/package/realm-env) package builds [MongoDB Realm](https://docs.mongodb.com/realm/) functions/triggers on multiple environments. Main purpose of this function is to avoid writing same function twice for development/stagin

Readme

Realm Env

Realm Env package builds MongoDB Realm functions/triggers on multiple environments. Main purpose of this function is to avoid writing same function twice for development/staging/production environments.

Setup

Install realm-env package in you application

$ npm install --save realm-env

OR

$ yarn add realm-env

Add script in package.json

{
  "scripts": {
    "build-realm": "realm-env ./config.json"
  },
}

After you are done configuring Realm Env you to build your application on multiple environments run

$ npm run build-realm

OR

$ yarn build-realm

Usage

you should wrap environment variables inside brackets

For example you have DB_NAME variable set inside environment syntax is as this follows

Env Usage

Configuration

To configure Realm Env you should create one JSON configuration file

Parameters:

  • functionsPath -> Path to your functions written in MongoDB Realm function syntax
  • triggersPath -> Path to your triggers written in MongoDB Realm trigger syntax
  • destFolder -> Path where generated files will be placed
  • realmConfig -> MongoDB Realm config.json file JSON Object
  • functions -> Formatted list of function objects with following format For Example you want to create deleteUsers function on dev environment Syntax is as it follows
{
  "functions": { // List of functions
    "deleteUsers": { // Function name
      "env": ["dev"] // List of function environments
    }
  },
}
  • triggers -> Formatted list of trigger objects with following format For Example you want to create deleteUsers trigger on dev environment Syntax is as it follows
{
  "triggers": { // List of triggers
    "deleteUsersTrigger": { // Trigger name
      "env": ["dev"] // List of triggers environments
    }
  },
}
  • env -> List of Environment Configuration. For example you want to share DB_NAME environment variable syntax is as it follows:
{
  "env": {
    "production": { // Environment Name
      "DB_NAME": "production" // Environment Variable
    },
    "staging": {
      "DB_NAME": "staging"
    },
    "dev": {
      "DB_NAME": "dev"
    }
  }
}

Example Configuration

Example configuration of Realm Application where you want to create deleteUsers function and trigger on dev and staging environment and share DB_NAME environment variable

{
  "functionsPath": "./src/functions",
  "triggersPath": "./src/triggers",
  "destFolder": "./build",
  "functions": {
    "deleteUsers": {
      "env": ["dev", "staging"]
    }
  },
  "triggers": {
    "deleteUsersTrigger": {
      "env": ["dev", "staging"]
    }
  },
  "realmConfig": {},
  "env": {
    "production": {
      "DB_NAME": "production"
    },
    "staging": {
      "DB_NAME": "staging"
    },
    "dev": {
      "DB_NAME": "dev"
    }
  }
}