All of these must be available in your
PATH. To verify things are set up
properly, you can run this:
git --version node --version npm --version
You may be able to work through the entire workshop in the browser. Go to this codesandbox and you should be good to go.
If you'd rather be able to work through the workshop on your own computer, then follow the following instructions.
After you've made sure to have the correct things (and versions) installed, you should be able to just run a few commands to get set up:
git clone https://github.com/kentcdodds/modern-react.git cd modern-react npm run setup --silent
This may take a few minutes. It will ask you for your email. This is optional and just automatically adds your email to the links in the project to make filling out some forms easier If you get any errors, please read through them and see if you can find out what the problem is. You may also want to look at Troubleshooting. If you can't work it out on your own then please file an issue and provide all the output from the commands you ran (even if it's a lot).
Running the app
To get the app up and running (and really see if it worked), run:
This should start up your browser. If you're familiar, this is a standard react-scripts application.
You can also open the deployment of the app on Netlify.
Running the tests
This will start Jest in watch mode. Read the output and play around with it.
Your goal will be to go into each test, swap the final version for the exercise version in the import, and make the tests pass
🐨 💰 💯
Each exercise has comments in it to help you get through the exercise.
Kody the Koala Bear and Marty the Money Bag are here to help you.
"npm run setup" command not working
Here's what the setup script does. If it fails, try doing each of these things individually yourself:
# verify your environment will work with the project node ./scripts/verify # install dependencies npm install # verify the project is ready to run npm run build npm run test:coverage
If any of those scripts fail, please try to work out what went wrong by the error message you get. If you still can't work it out, feel free to open an issue with all the output from that script. I will try to help if I can.
Thanks goes to these wonderful people (emoji key):
Kent C. Dodds
This project follows the all-contributors specification. Contributions of any kind welcome!