employee front end
This project was generated with ngX-Rocket version 1.3.3
Getting started
- Go to project folder and install dependencies:
npm install
- Launch development server, and open
localhost:4200
in your browser:
npm start
Main tasks
Task automation is based on NPM scripts.
Tasks | Description |
---|---|
npm start | Run development server on http://localhost:4200/ |
npm run build [-- --env=prod] | Lint code and build app for production in dist/ folder |
npm test | Run unit tests via Karma in watch mode |
npm run test:ci | Lint code and run unit tests once for continuous integration |
npm run e2e | Run e2e tests using Protractor |
npm run lint | Lint code |
npm run docs | Display project documentation |
When building the application, you can specify the target environment using the additional flag --env <name>
(do not
forget to prepend --
to pass arguments to npm scripts).
The default build environment is prod
.
Development server
Run npm start
for a dev server. Navigate to http://localhost:4200/
. The app will automatically reload if you change
any of the source files.
You should not use ng serve
directly, as it does not use the backend proxy configuration by default.
Code scaffolding
Run npm run generate -- component <name>
to generate a new component. You can also use
npm run generate -- directive|pipe|service|class|module
.
If you have installed angular-cli globally with npm install -g @angular/cli
,
you can also use the command ng generate
directly.
Additional tools
Tasks are mostly based on the angular-cli
tool. Use ng help
to get more help or go check out the
Angular-CLI README.
What's in the box
The app template is based on HTML5, TypeScript and Sass.
Tools
Development, build and quality processes are based on angular-cli and NPM scripts, which includes:
- Optimized build and bundling process with Webpack
- Development server with backend proxy and live reload
- Cross-browser CSS with autoprefixer and browserslist
- Asset revisioning for better cache management
- Unit tests using Jasmine and Karma
- End-to-end tests using Protractor
- Static code analysis: TSLint, Codelyzer, Stylelint and HTMLHint
- Local knowledgebase server using Hads