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

ng-process-env

v16.0.6

Published

**ng-process-env** will help you to retrieve values from System Environment variables (process.env) and update relevant `environment.ts` file.

Downloads

4,944

Readme

ng-process-env CI Process

Environment variables from process into Angular app

Angular already has its own environment system, which allows us to configure everything in src/environments/environment.ts, and we can create as many environments as we need. The problem is, sometimes you want to use the System Environment variables, for example, some configuration from the CI server or if the build process is running an "on-premise" server; in this case, the Angular environment system will not help.

ng-process-env will help you to retrieve values from System Environment variables (process.env[]) and update relevant environment.ts file.

Installing

Just add it into your app.

npm i ng-process-env

Run

ng g ng-process-env:process-env

For monorepo managed by NRWL, use nx command instead of ng

You will be prompted to insert relevant project name.

? Project name to update angular.json config. 
(you can skip and do it later using schematics or manually) my-app
 Project my-app will be updated
    Env File will be created at apps/my-app/src/environments
? You can set name for config to be updated or added as a new one, 'onprem' - default 

Define configuration name. It will create:

  • environment.<myconfig>.ts file in your /environments folder.
  • <myconfig> section in your angular.json or project.json for nrwl managed monorepo

environment..ts

export const environment = {
    production: false,
    baseUrl: 'http://localhost:4200',
    envVar: {
        /**
         * Add environment variables you want to retriev from process
         * PORT:4200,
         * VAR_NAME: defaultValue
         */
    }
};

angular.json \ project.json

{
  "targets": {
    "build": {
      ...
      "configurations": {
        "myconfig": {
          "fileReplacements": [
            {
              "replace": "apps/portfolio/src/environments/environment.ts",
              "with": "apps/portfolio/src/environments/environment.myconfig.ts"
            }
          ]
        }
      }
    }
  }
}

Update myconfig section according to your needs

Collect Vars

Open a created file environment.<myconfig>.ts

Update envVar section with variables you want to be retrieved from process.env.

  • Important: set default values.
export const environment = {
    production: false,
    baseUrl: 'http://localhost:4200',
    envVar: {
        myVarA: 3,
        myVarB: 'someValue'
    }
};

This part can be run during CI/CD process

To update the created environment..ts file with variables from process.env.

export myVarA=4
export myVarB=otherValue
ng run my-app:collect-vars

It will change file to:

export const environment = {
    production: false,
    baseUrl: "http://localhost:4200",
    envVar: {
        myVarA: 4 as number,
        myVarB: "otherValue"
    }
};

After it, you can run a build command.