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-http-env

v0.2.0

Published

Retrieve the environment configuration by HTTP on app startup.

Downloads

52

Readme

Runtime environment for Angular

Retrieve the environment configuration by HTTP on app startup.

Installation

#!/bin/bash
npm install --save ngx-http-env

Usage

Edit the main.ts such that the environment is loaded before app startup. This enables usage of the configuration in NgModules imported in the AppModule.

// main.ts

// (1) Add the following import
import { DYNAMIC_ENVIRONMENT, env } from 'ngx-http-env';

// (2) Move the original logic of main.ts to callback of subscribe
const url = '/assets/environments/environment.json?ngsw-bypass=true';
env(environment, url).subscribe(
  env => {

    // place the orinal logic of main.ts here
    if (env.production) {
      enableProdMode();
    }

    // (3) Add the following provider
    platformBrowserDynamic([{
      provide: DYNAMIC_ENVIRONMENT,
      useValue: env
    }])
    .bootstrapModule(AppModule)
    .catch(err => console.log(err));
  },
  err => console.error("Failed to load environment configuration", err)
)

After that, the global environment object was altered. It can be used to configure your app almost without changes.

IMPORTANT: Since environment is set dynamically, it must also be read dynamically. A build-time copy will not work

// wrong
private endpoint: string = `${environment.api}/endpoint`;
// right
private get endpoint(): string {  return `${environment.api}/endpoint`; }

Use dynamic environment to configure imported modules

If the imported module exports services that expect a configuration object to be injected, e.g. export class LibraryService(private config: LibraryServiceConfig), then a provider is required that depends on the injection token DYNAMIC_ENVIRONMENT.

// app.module.ts
import { DYNAMIC_ENVIRONMENT } from 'ngx-http-env';

@NgModule({
  declarations: [ /* ... */ ],
  imports: [
    LibraryModule
  ],
  providers: [
    // Provide the dependent modules
    { 
      provide: LibraryModuleConfig, 
      useFactory: (env:any) => env.libraryConfig,
      deps: [DYNAMIC_ENVIRONMENT]
    },
    /* ... */
  ],
  exports: [],
  bootstrap: [AppComponent]
})
export class AppModule {
  constructor() { }
}