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

@shellicar/build-azure-local-settings

v1.0.3

Published

Build plugin that loads Azure local.settings.json with Key Vault reference resolution for non-Azure-Functions apps.

Readme

@shellicar/build-azure-local-settings

npm package build status

Build plugin that loads Azure local.settings.json with Key Vault reference resolution for non-Azure-Functions apps.

  • Loads local.settings.json - Reads values and sets them as process.env variables before your app starts
  • Resolves Key Vault references - Fetches secrets from Azure Key Vault using DefaultAzureCredential (e.g. Azure CLI)
  • Local development only - Controlled via the loadLocalSettings option, typically tied to watch/dev mode

Installation & Quick Start

npm i --save-dev @shellicar/build-azure-local-settings
pnpm add -D @shellicar/build-azure-local-settings

esbuild

// build.ts
import plugin from '@shellicar/build-azure-local-settings/esbuild';
import esbuild from 'esbuild';

const watch = process.argv.includes('--watch');

const ctx = await esbuild.context({
  outdir: 'dist',
  bundle: true,
  platform: 'node',
  format: 'esm',
  plugins: [
    plugin({
      mainModule: './src/main.ts',
      loadLocalSettings: watch,
    }),
  ],
});

if (watch) {
  await ctx.watch();
} else {
  await ctx.rebuild();
  ctx.dispose();
}

tsup

// tsup.config.ts
import plugin from '@shellicar/build-azure-local-settings/esbuild';
import { defineConfig } from 'tsup';

export default defineConfig({
  esbuildPlugins: [
    plugin({
      mainModule: './src/main.ts',
    }),
  ],
});

How It Works

The plugin generates a virtual entry point that:

  1. Reads local.settings.json from the working directory
  2. Resolves any Key Vault references to their secret values
  3. Sets the resolved values as process.env variables
  4. Imports and runs your main module

Your application code accesses the values through process.env as normal:

// src/main.ts
export default async () => {
  console.log('Greeting:', process.env.GREETING_MESSAGE);
};

See examples for full working implementations.

@shellicar TypeScript Ecosystem

Core Libraries

Reference Architectures

Build Tools

Framework

Logging & Monitoring

Motivation

Azure Functions automatically loads local.settings.json and resolves Key Vault references during local development. Azure App Services and other Node.js apps don't have this capability.

This plugin brings that same behaviour to non-Functions apps, so you can:

  • Use the same local.settings.json config approach across Functions and App Services
  • Commit Key Vault references instead of secrets
  • Set up local dev with just Azure CLI access to Key Vault

Options

See types.ts for detailed options documentation.

Credits