seangwright/demo-ng-environment

Showcases abstracting an Angular CLI project that abstracts away access to environment.ts

NgEnvironment

In this app I use a service to abstract away access to the external filesystem dependency environment.ts.

This makes the app more testable and gives some added type-safety benefits to Environment configuration access by making it readonly.

Notable changes

src/environments/ienvironment.ts

src/environments/environment.*.ts

src/app/environment.service.ts

src/app/app.component.ts

src/app/app.component.spec.ts

Standard ng CLI boilerplace below ...

This project was generated with Angular CLI version 6.1.2.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.