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

@shellapps/config

v1.15.3

Published

Configuration management for ShellApps ecosystem

Readme

@shellapps/config

Configuration management for the ShellApps ecosystem. This package provides environment-specific configuration for all ShellApps and ShellLabs services.

Installation

npm install @shellapps/config

Usage

Basic Usage

import { getConfig } from '@shellapps/config';

const config = getConfig();
console.log(config.serviceUrls.apps); // https://apps.shellapps.com (in production)

Environment Configuration

The package reads the SHELLAPPS_ENV environment variable to determine which configuration to load:

  • development (default) - Local development with localhost URLs
  • staging - Staging environment with *.shellapps.net / *.shelllabs.net domains
  • production - Production environment with *.shellapps.com / *.shelllabs.net domains
# Set environment
export SHELLAPPS_ENV=production

# Or inline
SHELLAPPS_ENV=staging node app.js

Specific Configuration Getters

import { 
  getServiceUrls, 
  getS3Config, 
  getMongoConfig, 
  getFeatureFlags,
  getEnvironment 
} from '@shellapps/config';

// Get current environment
const env = getEnvironment(); // 'development' | 'staging' | 'production'

// Get service URLs
const urls = getServiceUrls();
console.log(urls.auth);    // Auth service URL
console.log(urls.apps);    // Main apps URL
console.log(urls.blog);    // Blog URL
console.log(urls.admin);   // ShellLabs admin URL

// Get S3 configuration
const s3 = getS3Config();
console.log(s3.buckets.assets);  // Asset bucket name
console.log(s3.buckets.uploads); // Upload bucket name

// Get MongoDB configuration
const mongo = getMongoConfig();
console.log(mongo.database);     // Database name
console.log(mongo.authDatabase); // Auth database name

// Get feature flags
const flags = getFeatureFlags();
console.log(flags.someFeature); // boolean value

Default Export

import config from '@shellapps/config';

const appConfig = config.getConfig();
const serviceUrls = config.getServiceUrls();
const s3Config = config.getS3Config();

TypeScript Types

All configuration objects are fully typed:

import type { 
  Config, 
  Environment, 
  ServiceUrls, 
  S3Config, 
  MongoConfig, 
  FeatureFlags 
} from '@shellapps/config';

function setupApp(config: Config) {
  // TypeScript will provide full intellisense and type checking
  const authUrl = config.serviceUrls.auth;
  const assetBucket = config.s3.buckets.assets;
}

Configuration Structure

Service URLs

  • Development: All services run on localhost with different ports
  • Staging: Uses *.shellapps.net and *.shelllabs.net domains
  • Production: Uses *.shellapps.com and *.shelllabs.net domains

S3 Buckets

Environment-specific bucket names:

  • Assets bucket: shellapps-{env}-assets
  • Uploads bucket: shellapps-{env}-uploads
  • Backups bucket: shellapps-{env}-backups

MongoDB

Environment-specific database names:

  • Development: shellapps_dev
  • Staging: shellapps_staging
  • Production: shellapps_production

Feature Flags

Object structure for enabling/disabling features per environment. Add flags as needed:

// In your app code
const flags = getFeatureFlags();
if (flags.newDashboard) {
  // Show new dashboard
}

Error Handling

The package throws descriptive errors for invalid configurations:

// If SHELLAPPS_ENV=invalid
try {
  const config = getConfig();
} catch (error) {
  console.error(error.message); 
  // "Invalid environment: invalid. Must be one of: development, staging, production"
}

Development

# Install dependencies
npm install

# Build the package
npm run build

# Watch for changes during development
npm run dev

# Clean build artifacts
npm run clean

License

MIT