Repository files navigation

React Fundamentals 🚀 EpicReact.Dev

Learn the foundational concepts necessary for building React applications and libraries

Learn everything you need to be effective with the fundamental building block of React applications. When you’re finished, you’ll be prepared to create React components to build excellent experiences for your app's users.

• Read through"JavaScript to Know for React"
• Install the React DevTools(Chrome(recommended),Firefox)

• git v2.13 or greater
• NodeJS^10.13 || 12 || 14 || 15
• npm v6 or greater

All of these must be available in yourPATH. To verify things are set upproperly, you can run this:

git --versionnode --versionnpm --version

If you have trouble with any of these, learn more about the PATH environmentvariable and how to fix it here forwindows ormac/linux.

If you want to commit and push your work as you go, you'll want toforkfirst and then clone your fork rather than this repo directly.

After you've made sure to have the correct things (and versions) installed, youshould be able to just run a few commands to get set up:

git clone https://github.com/kentcdodds/react-fundamentals.gitcd react-fundamentalsnode setup

This may take a few minutes.It will ask you for your email. This isoptional and just automatically adds your email to the links in the project tomake filling out some forms easier.

A few common issues duringnode setup have involved PATH variables (abovelinks orhere),reinstalling git, node, or npm, and clearing npm caches.

If you get any errors, please read through them and see if you can find out whatthe problem is. If you can't work it out on your own then pleasefile anissue and provideall the output from the commands you ran (even ifit's a lot).

If you can't get the setup script to work, then just make sure you have theright versions of the requirements listed above, and run the following commands:

npm installnpm run validate

If you are still unable to fix issues and you know how to use Docker 🐳 you cansetup the project with the following command:

docker-compose up

It's recommended you run everything locally in the same environment you work inevery day, but if you're having issues getting things set up, you can also setthis up usingGitHub Codespaces(video demo) orCodesandbox.

To get the app up and running (and really see if it worked), run:

npm start

This should start up your browser. If you're familiar, this is a standardreact-scripts application.

You can also openthe deployment of the app on Netlify.

npmtest

This will startJest in watch mode. Read the output andplay around with it. The tests are there to help you reach the final version,howeversometimes you can accomplish the task and the tests still fail if youimplement things differently than I do in my solution, so don't look to them asa complete authority.

• src/exercise/00.md: Background, Exercise Instructions, Extra Credit
• src/exercise/00.js: Exercise with Emoji helpers
• src/__tests__/00.js: Tests
• src/final/00.js: Final version
• src/final/00.extra-0.js: Final version of extra credit

The purpose of the exercise isnot for you to work through all the material.It's intended to get your brain thinking about the right questions to ask me asI walk through the material.

Each exercise has comments in it to help you get through the exercise. These funemoji characters are here to help you.

• Kody the Koala 🐨 will tell you when there's something specific you shoulddo
• Matthew the Muscle 💪 will indicate what you're working with an exercise
• Chuck the Checkered Flag 🏁 will indicate that you're working with a finalversion
• Marty the Money Bag 💰 will give you specific tips (and sometimes code)along the way
• Hannah the Hundred 💯 will give you extra challenges you can do if youfinish the exercises early.
• Olivia the Owl 🦉 will give you useful tidbits/best practice notes and alink for elaboration and feedback.
• Dominic the Document 📜 will give you links to useful documentation
• Berry the Bomb 💣 will be hanging around anywhere you need to blow stuffup (delete code)
• Peter the Product Manager 👨‍💼 helps us know what our users want
• Alfred the Alert 🚨 will occasionally show up in the test failures withpotential explanations for why the tests are failing.

Thanks goes to these wonderful people(emoji key):

Kent C. Dodds 💻📖🚇⚠️	Justin Dorfman 🔍	Ben Ilegbodu 📖	Jonathan Belcher 📖	Richard Hefner 💻	Zac Jones 📖	Ricardo Busquet 📖
Arpan Chattopadhyay 📖	Marco Moretti 💻	cindy 📖	Aaron Reisman 📖	Jacob M-G Evans 👀	Jesse Hull 📖	Tomas Caraccia 📖
Vasilii Kovalev 💻	Felix Geelhaar 📖	Apola Kipso 📖	dcgoodwin2112 🐛	Pritam Sangani 💻	Ryan Hinerman 📖💻	Marco 🐛
Peter Hozák 💻	Emmanouil Zoumpoulakis 📖	Navneet Sahota 📖	Rodrigo Fuentes 📖	Johnny Magrippis 💻	Roshan Acharya 📖	Art Telesh 📖💻
Amr A.Mohammed 🤔	Douglas 📖	Gaurav 💻	LauraOneasca 📖	Michaël De Boey 💻	Hannes Diercks ⚠️	Luke 🐛
Toni Dezman 💻	Bobby Warner 💻	Konrad Szałwiński 💻

This project follows theall-contributorsspecification. Contributions of any kind welcome!

Each exercise has an Elaboration and Feedback link. Please fill that out afterthe exercise and instruction.

At the end of the workshop, please go to this URL to give overall feedback.Thank you!https://kcd.im/rf-ws-feedback