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

ngx-runtime-env

v2.0.0

Published

<p align="center"> <img src="https://github.com/AleksanderBodurri/ngx-runtime-env/raw/main/logo.svg?" alt="ngx-runtime-env" width="350"/> </p>

Downloads

12

Readme

What problem does this library solve?

Many Angular applications depend on configuration to modify application behaviour. You may want multiple instances of the same Angular app to behave differently based on some configuration. Angular provides a way to do this at build time but often this solution is not flexible enough if engineers want to configure their app after it's been built/deployed.

ngx-runtime-env solves this. It fetches an application environment at runtime, and then mutates the existing Angular environment accordingly. See Usage for an example.

npm version AleksanderBodurri

Install

npm i ngx-runtime-env

or

yarn add ngx-runtime-env

Usage

In: src/environments/environment.ts (static)

export const environment = {
  production: false,
  foo: 'bar',
};

In: assets/environment.json (dynamic, picked up at runtime, will mutate static environment)

{
    "production": true,
    "foo": "baz",
}

In: app.module.ts

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { AppComponent } from './app.component';
import { HttpClientModule } from '@angular/common/http';
import { RuntimeEnvModule } from 'ngx-runtime-env';
import { environment } from '../environments/environment';

@NgModule({
  declarations: [ AppComponent ],
  imports: [ 
    BrowserModule,
    // import HttpClientModule
    HttpClientModule,
    // import RuntimeEnvModule module and pass in static environment
    RuntimeEnvModule.forRoot(environment)
  ],
  providers: [],
  bootstrap: [ AppComponent ]
})
export class AppModule {}

In a component (app.component.ts for example)

import { Component, OnInit } from '@angular/core';
import { environment } from 'src/environments/environment';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent implements OnInit {

  ngOnInit(): void {
    console.log(environment.production); // true
    console.log(environment.foo); // baz
  }
}

Configuration

| Name | Type | Default | Description | |---|---|---|---| | envUrl | string | assets/environment.json | Specify where the runtime environment can be found. | | bootstrapAppModule | 'before' \| 'after' | 'after' | Whether to bootstrap the application module before or after the runtime environment is loaded. | | optional | boolean | false | If true, application will bootstrap normally even if runtime environment fails to be found |

Example

In: app.module.ts

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { AppComponent } from './app.component';
import { HttpClientModule } from '@angular/common/http';
import { RuntimeEnvModule } from 'ngx-runtime-env';
import { environment } from '../environments/environment';

@NgModule({
  declarations: [ AppComponent ],
  imports: [ 
    BrowserModule,
    HttpClientModule,
    RuntimeEnvModule.forRoot(environment, {
      envUrl: '/path/to/my/config', // looks for runtime environment in envUrl
      bootstrapAppModule: 'before' // does not wait for runtime environment to bootstrap App Module
    })
  ],
  providers: [],
  bootstrap: [ AppComponent ]
})
export class AppModule {}