This project was created to show best practises of running a development/testing/deployment pipeline of Angular application using Heroku and Travis CI. Part of Swedbank IT Academy 2019.
The project was generated with Angular CLI version 7.3.1.
When in production, application can be launched via yarn start. It will use the server.js to launch a standalone server to handle proxying and static file serving.
API_URL - the URL of the backend API. Required
Run ng serve --proxy-config proxy.conf.json for a dev server (or you can just run yarn serve). Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
The file proxy.conf.json should be the same as proxy.conf.example.json but contain URL to your backend. This is done in order to avoid dealing with CORS (Read more: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS).
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.
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.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via Protractor.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.