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

@eschweitzer78/lwrjs-env-module-provider

v1.0.4

Published

A module provider for environment variables in LWR

Readme

lwrjs-env-module-provider

A module provider for environment variables in LWR

Purpose

Configuration of your apps through environment variables can be very convenient, especially when source code change and redeployment can be long or costly, or if you do want minimum downtime. This module provider enables you to import the value of environment variables (normally accessible under process.env) into your LWCs.

Configuration

The LWR server is configured in lwr.config.json, at the root of the project. You will need to configure the module providers to add the lwrjs-env-module-provider, which is available on npm as @eschweitzer78/lwrjs-env-module-provider.

Install it using npm i @eschweitzer78/lwrjs-env-module-provider

Then change the configuration file and remember to add all the standard module providers too.

// lwr.config.json
{
  "moduleProviders": [
    "@eschweitzer78/lwrjs-env-module-provider",
    "@lwrjs/app-service/moduleProvider",
    "@lwrjs/lwc-module-provider",
    "@lwrjs/npm-module-provider"
  ]
}

Getting environment variable values

In the code of your LWC, you can do a scoped import e.g:

import envValue from '@eschweitzer78/env/USERNAME';

You can then use the imported value as required, here is a full example:

// app.js
import { LightningElement } from 'lwc';

import envValue from '@eschweitzer78/env/USERNAME';

export default class HelloWorldApp extends LightningElement {
  get username() { return envValue; }
}
<!-- app.html -->
<template>
  <main>
    <img src="/public/assets/recipes-logo.png" alt="logo" />
      <h1>Hello {username}!</h1>
  </main>
</template>