This repo contains the course material for React Training. Before attending the training, please make sure you can run this repository.
First, install git and the LTS version of node. Then:
$ git clone https://github.com/ReactTraining/hooks-workshop.git
$ cd hooks-workshop
$ npm install
$ npm start
You'll be prompted with the exercise you'd like to run:
$ npm start
> [email protected] start ../hooks-workshop
> node scripts/start.js
Which exercise?
[1] 01-rendering
[2] 02-state
[3] 03-controlled-components
[4] 04-effects
[5] 05-data-loading
[6] 06-data-flow
[7] 07-compound-components
[8] 08-app-state
[9] 09-flicker
[a] 10-the-feed
[b] 11-animation
[c] 12-optimization
[0] THE FULL APP!
Choose one from list [1...9, a, b, c, 0]:
Choose option "0" to run the full app, then open a web browser to http://localhost:3000 to play around with it.
If you're having Internet problems and that's preventing you from logging into the app (because it uses Google Firebase), you can switch to "offline mode" which will use a local "fake" version of firebase. Just go to /modules/app/utils.js
and change this line:
// From this (line 1)
import { db, auth, mode } from "app/db.real.js"
// To this
import { db, auth, mode } from "app/db.fake.js"
During the lectures, feel free to take notes. We also have some pre-made notes for you in this repo that you can edit as you see fit.
If you've already cloned the repo but you need to get updated code, then follow these steps:
- First,
cd
into the root directory of the repo - Then do an
ls
command to ensure you see apackage.json
file listed. If you don't you're not in the root folder of the repo - Clear out any dirty files in your git working tree (
git stash
is a safe way to do it,git reset ---hard
is how to live dangerously) - Then run these steps to get the updates:
git pull origin master
npm install
Then you should be able to do your npm start
again.
IMPORTANT: Please read our JavaScript Primer before attending the workshop. It's a refresher on some of the newer bits of JavaScript you'll want to be familiar with in order to get the most out of the experience.
We'll be running commands like the ones from the install/update instructions above. These are bash commands which means if you're on Windows you'll need a bash-enabled command-line tool. If you've installed Git For Windows then you'll have a command-line tool called Git Bash already. This seems to work out well for doing other bash things that aren't just git specific (like npm).
A few common problems:
- You're having problems cloning the repository. Some corporate networks block port 22, which git uses to communicate with GitHub over SSH. Instead of using SSH, clone the repo over HTTPS. Use the following command to tell git to always use
https
instead ofgit
:
$ git config --global url."https://".insteadOf git://
# This adds the following to your `~/.gitconfig`:
[url "https://"]
insteadOf = git://
- You're having trouble installing node. We recommend using nvm. nvm makes it really easy to use multiple versions of node on the same machine painlessly. After you install nvm, install the latest stable version of node with the following command:
$ nvm use default stable
- You don't have permissions to install stuff. You might see an error like
EACCES
during thenpm install
step. If that's the case, it probably means that at some point you did ansudo npm install
and installed some stuff with root permissions. To fix this, you need to forcefully remove all files that npm caches on your machine and re-install without sudo.
$ sudo rm -rf node_modules
# If you installed node with nvm (suggested):
$ sudo rm -rf ~/.npm
# If you installed node with Homebrew:
$ sudo rm -rf /usr/local/lib/node_modules
# Then (look ma, no sudo!):
$ npm install
This material is available for private, non-commercial use under the GPL version 3. If you would like to use this material to conduct your own workshop, please contact us at [email protected].