This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Launches the test runner in CI mode.
Runs the lint:fix, test:ci and integration:concurrently:headless test scripts, make sure all passes before push to origin.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
-
Firstly, you have to run build, as the integration run script will serve static.
-
run 2 instances concurrently, 1 =
npm run blockchain, 1 =npm run integration -
to test a specific file, you will need run 2 instances concurrently, 1 =
npm run blockchain, 1 =npm run integration:single integration/<file name>.spec.ts
cross-env is required to run the npm scripts. It should be installed when running npm install
Encountered File name differs from already included file name only in casing error? Ensure that the absolute paths specified in the error are exactly the same and that the casings match.