yarn
yarn start
https://localhost:9090
should be opened automatically. Hot reloading of both react and static files (ejs, sass) files should work. Sometimes gulp forgets to watch new files so you need to rerun yarn start
.
We have to use https also during development as it is required by ledger to work correctly.
In .env.example
your will find all used env variables. When you do yarn start
this file will be copied as .env
(only if it doesn't exists already). If you want to change something modify .env
file which is gitignored. If you want to add new env variable make sure to add default to .env.example
.
- FAQ_ENABLED - 1 to display faq
- PLATFORM_ENABLED - 1 to display platform subpage
To autofix any errors just do yarn lint:fix
.
When working on diffrent branches and dependancies diverge, during merge/rebase huge yarn.lock conflicts will emerge. It would be unpractical to solve these problems manually. In order to cleanly install new dependancies while keeping old
lockfile configrations just do yarn fixyarn
.
yarn test
yarn test:coverage
yarn build
You will find all files in dist
directory.
Run yarn webpack:profile
to get build report. It should generate webpack-stats.json
file, unfortunately due to verbose typescript loader it will contain some logging. You need to delete few first lines with vim
. Then upload report to webpack-visualizer.
docker run -d -p 8545:8545 --name neufund-ico krzkaczor/neufund-ico # runs smartcontracts in docker
yarn test-e2e:dev # runs tests
docker rm -f neufund-ico # stops docker container