Environment Variables in Angular

Need to use different values depending on the environment you’re in? If you’re building an app that talks to the Stripe API for example, you’ll want to use your test publishable key during development and then your live publishable key in production. It’s easy to do in Angular using the environment.ts file.

This post applies to Angular 2+ apps.

🐊 Alligator.io recommends

Our recommended Angular courses

Angular CLI projects already use a production environment variable to enable production mode when in the production environment:


// ...

if (environment.production) {

// ...

And you’ll also notice that by default in the /src/environment folder you have an environment file for development and one for production. Let’s say we want to be a different animal depending if we’re in development or production mode:


export const environment = {
  production: false,
  animal: '🐊'


export const environment = {
  production: true,
  animal: '🐔'

And in our component all we have to do in order to access the variable is the following:


import { Component } from '@angular/core';
import { environment } from '../environments/environment';

@Component({ ... })
export class AppComponent {
  animal: string = environment.animal;

And it’s as simple as that! Angular takes care of swapping the environment file for the correct one.

Now in development mode the animal variable resolves to 🐊 and in production, if you run ng build --prod for example, animal resolves 🐔.

Detecting Development Mode With isDevMode()

Angular also provides us with an utility function called isDevMode that makes it easy to check if the app in running in dev mode:

import { Component, OnInit, isDevMode } from '@angular/core';

@Component({ ... })
export class AppComponent implements OnInit {
  ngOnInit() {
    if (isDevMode()) {
      console.log('👋 Development!');
    } else {
      console.log('💪 Production!');

Adding a Staging Environment

It’s easy to add new environments in Angular CLI projects by adding new entries to the environments field in the .angular-cli.json file. Let’s add a staging environment for example:


"environments": {
  "dev": "environments/environment.ts",
  "prod": "environments/environment.prod.ts",
  "staging": "environments/environment.staging.ts"

And now we can add a staging environment file and suddenly be a 🐻 if we build the project with ng build --env=staging:


export const environment = {
  production: true,
  animal: '🐻'
  Tweet It

🕵 Search Results

🔎 Searching...

Sponsored by #native_company# — Learn More
#native_title# #native_desc#