home
  • Blog
6.3
  • Introduction
  • Getting Started
  • Tutorial
  • Core Concepts
  • Components
  • Routing
  • Services
  • EmberData
  • In-Depth Topics
  • Application Development
  • Application Concerns
  • Accessibility
  • Configuration
  • Testing
  • Addons and Dependencies
  • Using TypeScript
  • Developer Tools
  • Ember Inspector
  • Code Editors
  • Additional Resources
  • Upgrading
  • Contributing to Ember.js
  • Glossary


Ember CLI ships with support for managing your application's environment. The runtime environment for the application is defined in config/environment.js. Here an object ENV is built for each of the three Ember CLI-supported build modes: development, test, and production.

Three notable properties on the ENV object are:

  • EmberENV can be used to define Ember feature flags (see the Feature Flags guide) to be enabled at runtime.
  • APP can be used to pass flags or options to the app's Application instance.
  • environment by default contains which of the build environments was selected at build time (development, test, or production).

The ENV object is defined at build time, but you can access the ENV object in application code via import from your-application-name/config/environment.

For example:

import ENV from 'your-application-name/config/environment';

if (ENV.environment === 'development') {
  // ...
}
Team Sponsors Security Legal Branding Community Guidelines
Twitter GitHub Discord Mastodon

If you want help you can contact us by email, open an issue, or get realtime help by joining the Ember Discord.

© Copyright 2025 - Tilde Inc.
Ember.js is free, open source and always will be.


Ember is generously supported by
blue Created with Sketch.