Make sure you have Node.js installed.
- Run
npm install
- Start the dev server using
npm start
- Open http://localhost:8080
npm start
- start the dev servernpm clean
- delete the dist foldernpm run production
- create a production ready build indist
foldernpm run lint
- execute an eslint checknpm test
- run all testsnpm run test:watch
- run all tests in watch modenpm run coverage
- generate code coverage report in thecoverage
folder
You can export specific vendors in separate files and load them. All vendors should be included in app/vendors
and will be exported in a vendors
folder under dist
. The main idea is to serve independent JavaScript and CSS libraries, though currently all file formats are supported.
! Don't forget to add the vendors in app/index.html
and build/index.html
.
The project is using the Jest Code Coverage tool. The reports are generated by running npm run coverage
. All configurations are located in package.json
, inside the jest
object.
The coverage report consists of an HTML reporter, which can be viewed in the browser and some helper coverage files like the coverage json and xml file.
Run npm run production
. The production-ready code will be located under dist
folder.
There are UAT, PreProd, and Production environments. Details of these environments and the entire system can be found in the Environment Details page of the wiki.
Configuration settings for the environments is managed in the Git Repo redbook-config-files/offer-management-tool. Deployment of these configuration values to the environments is done via the GoCD pipeline redbookci/offer-management-tool-config.
Deployment of the application itself is done via the GoCD pipeline redbookci/offer-management-tool-deployment. By default the pipeline deploys the last successful build on the "master" code branch.
ramda
pure functional library (highly recommended)date-fns
date and time related functions