This project is a testing ground for VA's foundation-react compoents. It was built using create-react-app which provided
the project's scaffolding. The rest were customizations needed to bring the components in and drop them all down on a
single page. The list of foundation-react components can be found here. For each component, I create a Container component to do things like show the value that was entered in a <div> or <p> element. The Container component is then added to App.js to display it.
You won't need to do this in order to run foundation-test. I just wanted to record the steps I took to set this project up for reference on new projects.
- Install node.js
- Install yarn
- Create a React.js application.
mkdir app
cd app
npx create-react-app .
- Add foundation and foundation-react dependencies to the app.
npm install --save @department-of-veterans-affairs/formation
npm install --save @department-of-veterans-affairs/formation-react
- Start the web server.
npm start
- In App.js, replace the JSX inside the parens () of the return statement in the App function with:
<div className="usa-width-one-whole">
</div>- In App.css, clear out the file and paste the following:
@import '../node_modules/@department-of-veterans-affairs/formation/dist/formation.min.css';- Create new componets in src/components and use them in App.js.
- React Developer Tools - NOTE: Also available for Microsft Edge (Chromium version).
EVERYTHING PAST THIS POINT WAS PART OF THE ORIGINAL README.MD THAT CREATE-REACT-APP CREATED
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.
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.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify