noteId: 12
user: 9493
wrote: Customer requests new product PROD30495
",
6 | "/application/DFG-20394/notes/45": "
Application Application : DFG-20394
noteId: 45
user: 8452
wrote: Advised customer that we don't have item in stock at the moment
",
7 | "/application/DFG-20394/notes/99": "
Note not found
",
8 | "test": "test"
9 | }
--------------------------------------------------------------------------------
/03-nested/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "navigatingreactrouter",
3 | "version": "0.0.1",
4 | "private": true,
5 | "devDependencies": {
6 | "react-scripts": "0.6.1"
7 | },
8 | "dependencies": {
9 | "react": "^15.3.2",
10 | "react-dom": "^15.3.2",
11 | "react-router": "^4.0.0-alpha.4"
12 | },
13 | "scripts": {
14 | "start": "react-scripts start",
15 | "build": "react-scripts build",
16 | "test": "react-scripts test --env=jsdom",
17 | "eject": "react-scripts eject"
18 | }
19 | }
20 |
--------------------------------------------------------------------------------
/03-nested/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gpltaylor/react-router-workshop/19d1437833dfc7d806c8e54a3a8f7db756a7311a/03-nested/public/favicon.ico
--------------------------------------------------------------------------------
/03-nested/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
16 |
React App
17 |
18 |
19 |
20 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/03-nested/src/App.css:
--------------------------------------------------------------------------------
1 | .App {
2 | text-align: center;
3 | }
4 |
5 | .App-logo {
6 | animation: App-logo-spin infinite 20s linear;
7 | height: 80px;
8 | }
9 |
10 | .App-header {
11 | background-color: #222;
12 | height: 150px;
13 | padding: 20px;
14 | color: white;
15 | }
16 |
17 | .App-intro {
18 | font-size: large;
19 | }
20 |
21 | @keyframes App-logo-spin {
22 | from { transform: rotate(0deg); }
23 | to { transform: rotate(360deg); }
24 | }
25 |
--------------------------------------------------------------------------------
/03-nested/src/App.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import logo from './logo.svg';
3 | import './App.css';
4 |
5 | import {Match, Miss} from 'react-router';
6 |
7 | import Navigation from './navigation';
8 | import Home from './home';
9 | import About from './aboutus';
10 | import NotFound from './notfound';
11 | import Application from './application';
12 |
13 | var App = () => {
14 | return (
15 |
16 |
17 |
18 |
Welcome to React
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 | )
29 | }
30 |
31 | export default App;
32 |
--------------------------------------------------------------------------------
/03-nested/src/aboutus.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 |
3 | var About = () => {
4 | return
5 |
About Us
6 |
A little bit about us
7 |
8 | }
9 |
10 | export default About;
11 |
--------------------------------------------------------------------------------
/03-nested/src/application.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import {Match, Link} from 'react-router';
3 | import Notes from "./notes";
4 | import Note from "./note";
5 |
6 | var application = ({pathname, params}) => {
7 | return
8 |
9 |
Application
10 |
Application : {params.appId}
11 |
12 |
13 |
14 | Notes
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 | }
23 |
24 | export default application;
25 |
--------------------------------------------------------------------------------
/03-nested/src/application/notes/noteService.js:
--------------------------------------------------------------------------------
1 | /*
2 | * A Mock notes service, this can be updated to connect to any endpoint
3 | */
4 | var notesData = [
5 | {noteId: 12, userId: 9493, message: 'Customer requests new product PROD30495'},
6 | {noteId: 45, userId: 8452, message: 'Advised customer that we don\'t have item in stock at the moment' },
7 | ];
8 |
9 | export default {
10 | getNotes: () => notesData
11 | };
12 |
--------------------------------------------------------------------------------
/03-nested/src/contact.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 |
3 | var Contact = ({location}) => {
4 | console.log("Contact", location);
5 |
6 | return
7 | {location.query == null ?
8 |
9 |
Contact
10 |
Please complete the following form
11 |
17 |
18 | :
19 |
20 |
Thank you, {location.query.firstName}!
21 |
{location.query.message}
22 |
23 | Your message shown above has been successfully submitted.
24 | We will be in contact with your shortly.
25 |
26 |
27 | }
28 |
29 | }
30 |
31 | export default Contact;
32 |
--------------------------------------------------------------------------------
/03-nested/src/home.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 |
3 | var Home = () => {
4 | return
5 |
Homes
6 |
Welcome to the best React Router Tutorial you will EVER see!!!! yeahhhh baby
7 |
8 | }
9 |
10 | export default Home;
11 |
--------------------------------------------------------------------------------
/03-nested/src/index.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin: 0;
3 | padding: 0;
4 | font-family: sans-serif;
5 | }
6 |
7 | ul li {
8 | list-style-type: none;
9 | display: inline;
10 | }
11 |
12 | li+li:before
13 | {
14 | content: ' | ';
15 | }
16 |
17 | .contact form {
18 | display: flex;
19 | width: 600px;
20 | margin-left: 20%;
21 | margin-right: 20%;
22 | }
23 |
24 | .contact form input {
25 | display: block;
26 | }
27 |
--------------------------------------------------------------------------------
/03-nested/src/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import Router from 'react-router/BrowserRouter';
4 |
5 | import App from './App';
6 |
7 | import './index.css';
8 |
9 | ReactDOM.render(
10 |
11 | ,
12 | document.getElementById('root')
13 | );
14 |
--------------------------------------------------------------------------------
/03-nested/src/logo.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/03-nested/src/navigation.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import Link from 'react-router/Link';
3 |
4 | var Navigation = () => {
5 | return
6 |
7 | Home
8 | About
9 | Application
10 |
11 |
12 | }
13 |
14 | export default Navigation;
15 |
--------------------------------------------------------------------------------
/03-nested/src/note.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import {Link} from 'react-router';
3 | import noteService from "./application/notes/noteService";
4 |
5 | var Note = ({params}) => {
6 | console.log("Note Render", params.id);
7 | var notesData = noteService.getNotes();
8 | var notes = notesData.filter(note => note.noteId === parseInt(params.id));
9 |
10 | if (notes === null || notes.length === 0) { return
Note not found
}
11 |
12 | var {noteId, userId, message} = notes[0];
13 |
14 | return (
15 |
16 |
noteId: {noteId}
17 |
user: {userId}
18 |
wrote: {message}
19 |
20 | )
21 | }
22 |
23 | var NoteRow = ({noteId, userId, message, pathname}) => {
24 | return (
25 |
26 | {noteId}
27 | {userId}
28 | {message}
29 | more
30 |
31 | )
32 | }
33 |
34 | export {NoteRow};
35 | export default Note;
36 |
--------------------------------------------------------------------------------
/03-nested/src/notes.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import {NoteRow} from "./note";
3 | import noteService from "./application/notes/noteService";
4 |
5 | var Notes = ({params, location, pathname}) => {
6 | console.log("Notes Render", params.id);
7 |
8 | var notesData = noteService.getNotes();
9 |
10 | return
11 |
Notes
12 |
See the notes for this applications
13 |
14 |
15 |
16 |
17 | Id
18 | User
19 | msg
20 |
21 |
22 |
23 |
24 | {notesData.map(note => )}
25 |
26 |
27 |
28 |
29 | }
30 |
31 | export default Notes;
32 |
--------------------------------------------------------------------------------
/03-nested/src/notfound.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 |
3 | var NotFound = ({location}) => {
4 | return
5 |
Not Found
6 |
Sorry but the page can not be found.
7 |
8 | }
9 |
10 | export default NotFound;
11 |
--------------------------------------------------------------------------------
/04-transitions/.gitignore:
--------------------------------------------------------------------------------
1 | # See http://help.github.com/ignore-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | node_modules
5 |
6 | # testing
7 | coverage
8 |
9 | # production
10 | build
11 |
12 | # misc
13 | .DS_Store
14 | .env
15 | npm-debug.log
16 |
--------------------------------------------------------------------------------
/04-transitions/README.md:
--------------------------------------------------------------------------------
1 | # React Router Tutoral
2 | A collection of simple examples, demonstrating the power of the latest React Router Version 4
3 |
4 | * NavigationPrompt
5 | * FadeIn
6 |
7 | ## NavigationPrompt
8 | Allow you to control if the user is allowed to navigate away from the component.
9 |
10 | ## FadeIn
11 | Shows an example of extending the Match component and add custom functionality.
12 | Common reasons to extend are for animation and security.
--------------------------------------------------------------------------------
/04-transitions/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "navigatingreactrouter-transitions",
3 | "version": "0.0.1",
4 | "private": true,
5 | "devDependencies": {
6 | "react-scripts": "0.6.1"
7 | },
8 | "dependencies": {
9 | "react": "^15.3.2",
10 | "react-dom": "^15.3.2",
11 | "react-router": "next",
12 | "react-router-dom": "^4.1.1"
13 | },
14 | "scripts": {
15 | "start": "react-scripts start",
16 | "build": "react-scripts build",
17 | "test": "react-scripts test --env=jsdom",
18 | "eject": "react-scripts eject"
19 | }
20 | }
21 |
--------------------------------------------------------------------------------
/04-transitions/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gpltaylor/react-router-workshop/19d1437833dfc7d806c8e54a3a8f7db756a7311a/04-transitions/public/favicon.ico
--------------------------------------------------------------------------------
/04-transitions/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
16 |
React App
17 |
18 |
19 |
20 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/04-transitions/src/App.css:
--------------------------------------------------------------------------------
1 | .App {
2 | text-align: center;
3 | }
4 |
5 | .App-logo {
6 | animation: App-logo-spin infinite 20s linear;
7 | height: 80px;
8 | }
9 |
10 | .App-header {
11 | background-color: #222;
12 | height: 150px;
13 | padding: 20px;
14 | color: white;
15 | }
16 |
17 | .App-intro {
18 | font-size: large;
19 | }
20 |
21 | .App-main {
22 | padding-left: 15px;
23 | padding-right: 15px;
24 | text-align: left;
25 | }
26 |
27 | @keyframes App-logo-spin {
28 | from { transform: rotate(0deg); }
29 | to { transform: rotate(360deg); }
30 | }
31 |
32 | nav li+li:before
33 | {
34 | content: ' | ';
35 | }
36 |
37 | nav ul {
38 | display: flex;
39 | }
40 | nav ul li {
41 | list-style-type: none;
42 | display: block;
43 |
44 | }
45 |
--------------------------------------------------------------------------------
/04-transitions/src/App.js:
--------------------------------------------------------------------------------
1 | import React, { Component } from 'react';
2 | import ReactDOM from 'react-dom';
3 |
4 | import { Switch, Route, Link } from 'react-router-dom';
5 |
6 | import Home from './home';
7 | import Aboutus from './aboutus';
8 | import AppForm from './AppForm';
9 |
10 | import logo from './logo.svg';
11 | import './App.css';
12 |
13 | class FadeIn extends Component {
14 |
15 | componentDidMount() {
16 | console.log("componentDidMount", this.displayName);
17 | var that = this;
18 | // Get the components DOM node
19 | var elem = ReactDOM.findDOMNode(that);
20 | // Set the opacity of the element to 0
21 | elem.style.opacity = 0;
22 | window.requestAnimationFrame(function () {
23 | // Now set a transition on the opacity
24 | elem.style.transition = that.props.transition || "opacity 5000ms";
25 | // and set the opacity to 1
26 | elem.style.opacity = 1;
27 | });
28 | }
29 |
30 | render() {
31 | return (
32 |
33 | {this.props.children}
34 |
35 | )
36 | }
37 | }
38 |
39 | const MatchWithFade = ({ component: Component, transition, ...rest }) => (
40 |
(
41 |
42 |
43 |
44 | )} />
45 | )
46 |
47 | class App extends Component {
48 |
49 | render() {
50 |
51 | return (
52 |
53 |
54 |
55 |
Welcome to React
56 |
Intro to Transitions
57 |
58 |
59 |
60 | Home
61 | About Us
62 | Apply
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 | );
72 | }
73 | }
74 |
75 | export default App;
76 |
--------------------------------------------------------------------------------
/04-transitions/src/App.test.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import Router from 'react-router/BrowserRouter'
4 | import App from './App';
5 |
6 | it('renders without crashing', () => {
7 | const div = document.createElement('div');
8 | ReactDOM.render( , div);
9 | });
10 |
--------------------------------------------------------------------------------
/04-transitions/src/AppForm.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import { Prompt } from 'react-router-dom';
3 |
4 | class AppForm extends React.Component {
5 | constructor() {
6 | super();
7 | this.state = {
8 | blockTransitions: false,
9 | firstName: '',
10 | surname: ''
11 | }
12 |
13 | this.onChange = this.onChange.bind(this);
14 | this.submit = this.submit.bind(this);
15 | }
16 |
17 | onChange(e) {
18 | this.setState({[e.target.name]: e.target.value, blockTransitions: true});
19 | }
20 |
21 | submit() {
22 | this.setState({blockTransitions: false, status:'Thank you, your application has been submitted.'});
23 | }
24 |
25 | render() {
26 | return (
27 |
43 | )
44 | }
45 | }
46 |
47 | export default AppForm;
48 |
--------------------------------------------------------------------------------
/04-transitions/src/aboutus.js:
--------------------------------------------------------------------------------
1 | import * as React from "react";
2 |
3 | const Aboutus = () => (
4 |
5 |
About Us
6 |
7 | )
8 |
9 | export default Aboutus;
--------------------------------------------------------------------------------
/04-transitions/src/home.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 |
3 | var Home = () =>
4 |
Welcome
5 |
To the best React Router tutorial in the world!
6 |
7 |
8 | export default Home;
9 |
--------------------------------------------------------------------------------
/04-transitions/src/index.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin: 0;
3 | padding: 0;
4 | font-family: sans-serif;
5 | }
6 |
--------------------------------------------------------------------------------
/04-transitions/src/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import { BrowserRouter as Router } from 'react-router-dom';
4 | import App from './App';
5 | import './index.css';
6 |
7 | window.Router = Router;
8 |
9 | ReactDOM.render( ,
10 | document.getElementById('root')
11 | );
12 |
--------------------------------------------------------------------------------
/04-transitions/src/logo.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/05-redux/.gitignore:
--------------------------------------------------------------------------------
1 | # See http://help.github.com/ignore-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | node_modules
5 |
6 | # testing
7 | coverage
8 |
9 | # production
10 | build
11 |
12 | # misc
13 | .DS_Store
14 | .env
15 | npm-debug.log
16 |
--------------------------------------------------------------------------------
/05-redux/README.md:
--------------------------------------------------------------------------------
1 | # React Router Tutoral - Redux
2 | Using a State management system is becoming very popular and Redux is currently winning this war.
3 | This tutorial shows how to use Redux to navigate around your application.
4 |
--------------------------------------------------------------------------------
/05-redux/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "navigatingreactroutertransitions",
3 | "version": "0.0.1",
4 | "private": true,
5 | "devDependencies": {
6 | "react-scripts": "0.6.1"
7 | },
8 | "dependencies": {
9 | "react": "^15.3.2",
10 | "react-dom": "^15.3.2",
11 | "react-redux": "^4.4.5",
12 | "react-router": "^4.0.0",
13 | "react-router-addons-controlled": "0.0.1",
14 | "react-router-dom": "^4.0.0-beta.8",
15 | "react-router-redux": "^5.0.0-alpha.4",
16 | "redux": "^3.6.0",
17 | "redux-devtools-extension": "^1.0.0",
18 | "redux-thunk": "^2.1.0"
19 | },
20 | "scripts": {
21 | "start": "react-scripts start",
22 | "build": "react-scripts build",
23 | "test": "react-scripts test --env=jsdom",
24 | "eject": "react-scripts eject"
25 | }
26 | }
27 |
--------------------------------------------------------------------------------
/05-redux/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gpltaylor/react-router-workshop/19d1437833dfc7d806c8e54a3a8f7db756a7311a/05-redux/public/favicon.ico
--------------------------------------------------------------------------------
/05-redux/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
16 | React App
17 |
18 |
19 |
20 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/05-redux/src/App.css:
--------------------------------------------------------------------------------
1 | .App {
2 | text-align: center;
3 | }
4 |
5 | .App-logo {
6 | animation: App-logo-spin infinite 20s linear;
7 | height: 80px;
8 | }
9 |
10 | .App-header {
11 | background-color: #222;
12 | height: 150px;
13 | padding: 20px;
14 | color: white;
15 | }
16 |
17 | .App-intro {
18 | font-size: large;
19 | }
20 |
21 | .App-main {
22 | padding-left: 15px;
23 | padding-right: 15px;
24 | text-align: left;
25 | }
26 |
27 | @keyframes App-logo-spin {
28 | from { transform: rotate(0deg); }
29 | to { transform: rotate(360deg); }
30 | }
31 |
32 | nav li+li:before
33 | {
34 | content: ' | ';
35 | }
36 |
37 | nav ul {
38 | display: flex;
39 | }
40 | nav ul li {
41 | list-style-type: none;
42 | display: block;
43 |
44 | }
45 |
--------------------------------------------------------------------------------
/05-redux/src/App.js:
--------------------------------------------------------------------------------
1 | import React, { Component } from 'react';
2 |
3 | import { Route } from 'react-router-dom';
4 |
5 | import Home from './home';
6 | import AppForm from './AppForm';
7 | import Navigation from "./Navigation";
8 |
9 | import logo from './logo.svg';
10 | import './App.css';
11 | import './index.css';
12 |
13 | class App extends Component {
14 |
15 | render() {
16 |
17 | return (
18 |
19 |
20 |
21 |
React Router Redux
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | );
30 | }
31 | }
32 |
33 | export default App;
34 |
--------------------------------------------------------------------------------
/05-redux/src/App.test.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import Router from 'react-router/BrowserRouter'
4 | import App from './App';
5 |
6 | it('renders without crashing', () => {
7 | const div = document.createElement('div');
8 | ReactDOM.render( , div);
9 | });
10 |
--------------------------------------------------------------------------------
/05-redux/src/AppForm.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import { Prompt } from 'react-router';
3 | import { connect } from 'react-redux';
4 | import { push } from "react-router-redux";
5 |
6 | class AppFormComponent extends React.Component {
7 | constructor() {
8 | super();
9 | this.state = {
10 | blockTransitions: false,
11 | firstName: '',
12 | surname: ''
13 | }
14 |
15 | this.onChange = this.onChange.bind(this);
16 | this.submit = this.submit.bind(this);
17 | }
18 |
19 | onChange(e) {
20 | this.setState({blockTransitions: true });
21 | this.props.updateForm(e.target.name, e.target.value);
22 | }
23 |
24 | submit() {
25 | this.setState({
26 | blockTransitions: false,
27 | status:'Thank you, your application has been submitted.'
28 | }, () => {
29 | this.props.navigateTo('/');
30 | });
31 | }
32 |
33 | render() {
34 | return (
35 |
50 | )
51 | }
52 | }
53 |
54 | const state = (state, ownProps = {}) => {
55 | return {
56 | firstName: state.register.firstName,
57 | surname: state.register.surname,
58 | age: state.register.age
59 | }
60 | }
61 |
62 | const mapDispatchToProps = (dispatch, ownProps) => ({
63 | navigateTo: (location) => {
64 | dispatch(push('/'))
65 | },
66 | updateForm: (key, value) => {
67 | dispatch( { type: "REGISTER_FORM_UPDATE", key, value });
68 | }
69 | });
70 |
71 | export default connect(state, mapDispatchToProps)(AppFormComponent);
--------------------------------------------------------------------------------
/05-redux/src/Navigation.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import {connect} from "react-redux";
3 | import { push } from "react-router-redux";
4 |
5 | let NavigationComponent = (props) => (
6 |
7 |
11 |
12 | )
13 |
14 | const state = (state, ownProps = {}) => {
15 | return {
16 | location: state.location
17 | }
18 | }
19 |
20 | const mapDispatchToProps = (dispatch, ownProps) => ({
21 | navigateTo: (location) => {
22 | dispatch(push(location));
23 | }
24 | });
25 |
26 | export default connect(state, mapDispatchToProps)(NavigationComponent);
--------------------------------------------------------------------------------
/05-redux/src/home.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 |
3 | var Home = () =>
4 |
Welcome to React Router Redux
5 |
Here we are going to show you how to implement support for routing your Redux!
6 |
7 |
8 | export default Home;
9 |
--------------------------------------------------------------------------------
/05-redux/src/index.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin: 0;
3 | padding: 0;
4 | font-family: sans-serif;
5 | }
6 |
--------------------------------------------------------------------------------
/05-redux/src/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from "react-dom";
3 |
4 | import { Provider } from "react-redux";
5 | import { ConnectedRouter as Router, routerReducer, routerMiddleware } from "react-router-redux";
6 | import { createStore, applyMiddleware, combineReducers } from "redux";
7 |
8 | import { composeWithDevTools } from 'redux-devtools-extension';
9 |
10 | import thunk from "redux-thunk";
11 | import createHistory from 'history/createBrowserHistory';
12 |
13 | const history = createHistory();
14 | const middleware = routerMiddleware(history);
15 |
16 | import registerReducer from "./reducers/register";
17 |
18 | import App from './App';
19 |
20 | const reducers = combineReducers({ register: registerReducer, router: routerReducer });
21 | const store = createStore(reducers, composeWithDevTools(applyMiddleware(middleware, thunk)));
22 |
23 | ReactDOM.render(
24 |
25 |
26 |
27 |
30 |
31 | ,
32 | document.getElementById('root')
33 | );
34 |
--------------------------------------------------------------------------------
/05-redux/src/logo.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/05-redux/src/reducers/register.js:
--------------------------------------------------------------------------------
1 | const initialState = {
2 | firstName: '',
3 | surname: '',
4 | age: ''
5 | };
6 |
7 | const registerReducer = (state = initialState, action) => {
8 | switch (action.type) {
9 | case "REGISTER_FORM_UPDATE":
10 | return Object.assign({}, state, { [action.key]: action.value });
11 | default:
12 | return state;
13 | }
14 | }
15 |
16 | export default registerReducer;
--------------------------------------------------------------------------------
/06-Prompt/README.md:
--------------------------------------------------------------------------------
1 | # Custom Prompt
2 | The default NavigationPrompt uses window.confim to display the dialog.
3 | In some cases this is not good enough and you may wish to extend this logic.
4 | Within this demo we should how to use the props "getUserConfirmation" to provide
5 | custom logic.
6 |
7 | ## Hash Router
8 | This example also uses a different Router type, Hash Router. This uses the old-school
9 | hash method of changing the URL.
--------------------------------------------------------------------------------
/06-Prompt/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "navigatingreactrouterprompt",
3 | "version": "0.0.1",
4 | "private": true,
5 | "devDependencies": {
6 | "react-scripts": "0.7.0"
7 | },
8 | "dependencies": {
9 | "react": "^15.4.1",
10 | "react-dom": "^15.4.1",
11 | "react-router": "^4.0.0-alpha.6"
12 | },
13 | "scripts": {
14 | "start": "react-scripts start",
15 | "build": "react-scripts build",
16 | "test": "react-scripts test --env=jsdom",
17 | "eject": "react-scripts eject"
18 | }
19 | }
20 |
--------------------------------------------------------------------------------
/06-Prompt/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gpltaylor/react-router-workshop/19d1437833dfc7d806c8e54a3a8f7db756a7311a/06-Prompt/public/favicon.ico
--------------------------------------------------------------------------------
/06-Prompt/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
16 | React App
17 |
18 |
19 |
20 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/06-Prompt/src/App.css:
--------------------------------------------------------------------------------
1 | .App {
2 | text-align: center;
3 | }
4 |
5 | .App-logo {
6 | animation: App-logo-spin infinite 20s linear;
7 | height: 80px;
8 | }
9 |
10 | .App-header {
11 | background-color: #222;
12 | height: 150px;
13 | padding: 20px;
14 | color: white;
15 | }
16 |
17 | .App-intro {
18 | font-size: large;
19 | }
20 |
21 | @keyframes App-logo-spin {
22 | from { transform: rotate(0deg); }
23 | to { transform: rotate(360deg); }
24 | }
25 |
--------------------------------------------------------------------------------
/06-Prompt/src/App.js:
--------------------------------------------------------------------------------
1 | import React, { Component } from 'react';
2 | import { Match } from 'react-router';
3 | import Link from 'react-router/Link';
4 | import logo from './logo.svg';
5 | import './App.css';
6 | import createHistory from 'history/createBrowserHistory';
7 |
8 | let About = () => About us ;
9 | let FAQ = () => FAQ ;
10 |
11 | class App extends Component {
12 | constructor() {
13 | super();
14 | this.history = createHistory();
15 | }
16 |
17 | goBack() {
18 | history.back();
19 | }
20 |
21 | render() {
22 | return (
23 |
24 |
25 |
26 |
Welcome to React
27 |
28 | About us
29 | FAQ
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 | );
39 | }
40 | }
41 |
42 | export default App;
43 |
--------------------------------------------------------------------------------
/06-Prompt/src/App.test.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import App from './App';
4 |
5 | it('renders without crashing', () => {
6 | const div = document.createElement('div');
7 | ReactDOM.render( , div);
8 | });
9 |
--------------------------------------------------------------------------------
/06-Prompt/src/index.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin: 0;
3 | padding: 0;
4 | font-family: sans-serif;
5 | }
6 |
--------------------------------------------------------------------------------
/06-Prompt/src/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import Router from 'react-router/HashRouter';
4 | import NavigationPrompt from 'react-router/NavigationPrompt';
5 | import App from './App';
6 | import './index.css';
7 |
8 | let getUserConfirmation = (message, callback) => {
9 | let success = () => {
10 | alert("Success");
11 | callback(true);
12 | };
13 |
14 | let failed = () => {
15 | alert("Failed");
16 | callback(false);
17 | }
18 |
19 | let doWork = new Promise((resolve, reject) => {
20 | Math.random() > 0.5 ?
21 | resolve("This is ok") :
22 | reject("Something went wrong");
23 | });
24 |
25 | doWork.then(success,failed);
26 | }
27 |
28 | class CustomUserConfirmation extends React.Component {
29 | constructor(props) {
30 | super(props);
31 | this.state = {answer: false, question: props.question};
32 | }
33 |
34 | render() {
35 | return (
36 |
37 |
38 |
39 | )
40 | }
41 | }
42 |
43 | ReactDOM.render(
44 |
48 | ,
49 | document.getElementById('root'));
50 |
--------------------------------------------------------------------------------
/06-Prompt/src/logo.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/07-Navigation/README.md:
--------------------------------------------------------------------------------
1 | # Custom Prompt
2 | The default NavigationPrompt uses window.confim to display the dialog.
3 | In some cases this is not good enough and you may wish to extend this logic.
4 | Within this demo we should how to use the props "getUserConfirmation" to provide
5 | custom logic.
6 |
7 | ## Hash Router
8 | This example also uses a different Router type, Hash Router. This uses the old-school
9 | hash method of changing the URL.
--------------------------------------------------------------------------------
/07-Navigation/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "navigatingreactrouternavigation",
3 | "version": "0.0.1",
4 | "private": true,
5 | "devDependencies": {
6 | "react-scripts": "0.7.0"
7 | },
8 | "dependencies": {
9 | "react": "^15.4.1",
10 | "react-dom": "^15.4.1",
11 | "react-router": "^4.0.0-alpha.6"
12 | },
13 | "scripts": {
14 | "start": "react-scripts start",
15 | "build": "react-scripts build",
16 | "test": "react-scripts test --env=jsdom",
17 | "eject": "react-scripts eject"
18 | }
19 | }
20 |
--------------------------------------------------------------------------------
/07-Navigation/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gpltaylor/react-router-workshop/19d1437833dfc7d806c8e54a3a8f7db756a7311a/07-Navigation/public/favicon.ico
--------------------------------------------------------------------------------
/07-Navigation/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
16 | React App
17 |
18 |
19 |
20 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/07-Navigation/src/App.css:
--------------------------------------------------------------------------------
1 | .App {
2 | text-align: center;
3 | }
4 |
5 | .App-logo {
6 | animation: App-logo-spin infinite 20s linear;
7 | height: 80px;
8 | }
9 |
10 | .App-header {
11 | background-color: #222;
12 | height: 150px;
13 | padding: 20px;
14 | color: white;
15 | }
16 |
17 | .App-intro {
18 | font-size: large;
19 | }
20 |
21 | @keyframes App-logo-spin {
22 | from { transform: rotate(0deg); }
23 | to { transform: rotate(360deg); }
24 | }
25 |
--------------------------------------------------------------------------------
/07-Navigation/src/App.js:
--------------------------------------------------------------------------------
1 | import React, { Component } from 'react';
2 | import { Match } from 'react-router';
3 | import logo from './logo.svg';
4 | import './App.css';
5 |
6 | import Redirector from "./redirector";
7 | let About = () => About us ;
8 | let FAQ = () => FAQ ;
9 |
10 | class App extends Component {
11 | constructor() {
12 | super();
13 | this.transitionTo = this.transitionTo.bind(this);
14 | }
15 |
16 | transitionTo(e) {
17 | e.preventDefault();
18 | this.context.router.transitionTo(e.target.pathname);
19 | // this.context.router.replaceWith(location);
20 | }
21 |
22 | render() {
23 | return (
24 |
25 |
26 |
27 |
Welcome to React
28 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 | );
41 | }
42 | }
43 |
44 | App.contextTypes = {
45 | router: React.PropTypes.object
46 | };
47 |
48 | export default App;
49 |
--------------------------------------------------------------------------------
/07-Navigation/src/App.test.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import Router from 'react-router-dom/BrowserRouter';
4 | import App from './App';
5 |
6 | it('renders without crashing', () => {
7 | const div = document.createElement('div');
8 | ReactDOM.render(
9 |
10 | , div);
11 | });
12 |
--------------------------------------------------------------------------------
/07-Navigation/src/index.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin: 0;
3 | padding: 0;
4 | font-family: sans-serif;
5 | }
6 |
--------------------------------------------------------------------------------
/07-Navigation/src/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import Router from 'react-router/BrowserRouter';
4 | import App from './App';
5 | import './index.css';
6 |
7 | ReactDOM.render(
8 |
9 | , document.getElementById('root'));
10 |
--------------------------------------------------------------------------------
/07-Navigation/src/logo.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/07-Navigation/src/redirector.js:
--------------------------------------------------------------------------------
1 | import * as React from "react";
2 | import {Redirect} from "react-router";
3 |
4 | class Redirector extends React.Component {
5 | constructor(props) {
6 | super(props);
7 | this.update = this.update.bind(this);
8 | this.state = {
9 | to: "/",
10 | push: false
11 | }
12 | }
13 |
14 | update(e) {
15 | if(e.target.name === "push") {
16 | this.setState({push: e.target.checked });
17 | console.log("update", e.target.checked);
18 | return;
19 | }
20 |
21 | this.setState({[e.target.name]: e.target.value});
22 | }
23 |
24 | render() {
25 | return (
26 |
42 | )
43 | }
44 | }
45 |
46 | export default Redirector;
--------------------------------------------------------------------------------
/08-switch/.gitignore:
--------------------------------------------------------------------------------
1 | # See https://help.github.com/ignore-files/ for more about ignoring files.
2 |
3 | # dependencies
4 | /node_modules
5 |
6 | # testing
7 | /coverage
8 |
9 | # production
10 | /build
11 |
12 | # misc
13 | .DS_Store
14 | .env
15 | npm-debug.log*
16 | yarn-debug.log*
17 | yarn-error.log*
18 |
19 |
--------------------------------------------------------------------------------
/08-switch/README.md:
--------------------------------------------------------------------------------
1 | This project was bootstrapped with [Create React App](https://github.com/facebookincubator/create-react-app).
2 |
3 | Below you will find some information on how to perform common tasks.
4 | You can find the most recent version of this guide [here](https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md).
5 |
6 | ## Table of Contents
7 |
8 | - [Updating to New Releases](#updating-to-new-releases)
9 | - [Sending Feedback](#sending-feedback)
10 | - [Folder Structure](#folder-structure)
11 | - [Available Scripts](#available-scripts)
12 | - [npm start](#npm-start)
13 | - [npm test](#npm-test)
14 | - [npm run build](#npm-run-build)
15 | - [npm run eject](#npm-run-eject)
16 | - [Supported Language Features and Polyfills](#supported-language-features-and-polyfills)
17 | - [Syntax Highlighting in the Editor](#syntax-highlighting-in-the-editor)
18 | - [Displaying Lint Output in the Editor](#displaying-lint-output-in-the-editor)
19 | - [Debugging in the Editor](#debugging-in-the-editor)
20 | - [Changing the Page ``](#changing-the-page-title)
21 | - [Installing a Dependency](#installing-a-dependency)
22 | - [Importing a Component](#importing-a-component)
23 | - [Adding a Stylesheet](#adding-a-stylesheet)
24 | - [Post-Processing CSS](#post-processing-css)
25 | - [Adding a CSS Preprocessor (Sass, Less etc.)](#adding-a-css-preprocessor-sass-less-etc)
26 | - [Adding Images and Fonts](#adding-images-and-fonts)
27 | - [Using the `public` Folder](#using-the-public-folder)
28 | - [Changing the HTML](#changing-the-html)
29 | - [Adding Assets Outside of the Module System](#adding-assets-outside-of-the-module-system)
30 | - [When to Use the `public` Folder](#when-to-use-the-public-folder)
31 | - [Using Global Variables](#using-global-variables)
32 | - [Adding Bootstrap](#adding-bootstrap)
33 | - [Using a Custom Theme](#using-a-custom-theme)
34 | - [Adding Flow](#adding-flow)
35 | - [Adding Custom Environment Variables](#adding-custom-environment-variables)
36 | - [Referencing Environment Variables in the HTML](#referencing-environment-variables-in-the-html)
37 | - [Adding Temporary Environment Variables In Your Shell](#adding-temporary-environment-variables-in-your-shell)
38 | - [Adding Development Environment Variables In `.env`](#adding-development-environment-variables-in-env)
39 | - [Can I Use Decorators?](#can-i-use-decorators)
40 | - [Integrating with an API Backend](#integrating-with-an-api-backend)
41 | - [Node](#node)
42 | - [Ruby on Rails](#ruby-on-rails)
43 | - [Proxying API Requests in Development](#proxying-api-requests-in-development)
44 | - [Using HTTPS in Development](#using-https-in-development)
45 | - [Generating Dynamic ` ` Tags on the Server](#generating-dynamic-meta-tags-on-the-server)
46 | - [Pre-Rendering into Static HTML Files](#pre-rendering-into-static-html-files)
47 | - [Injecting Data from the Server into the Page](#injecting-data-from-the-server-into-the-page)
48 | - [Running Tests](#running-tests)
49 | - [Filename Conventions](#filename-conventions)
50 | - [Command Line Interface](#command-line-interface)
51 | - [Version Control Integration](#version-control-integration)
52 | - [Writing Tests](#writing-tests)
53 | - [Testing Components](#testing-components)
54 | - [Using Third Party Assertion Libraries](#using-third-party-assertion-libraries)
55 | - [Initializing Test Environment](#initializing-test-environment)
56 | - [Focusing and Excluding Tests](#focusing-and-excluding-tests)
57 | - [Coverage Reporting](#coverage-reporting)
58 | - [Continuous Integration](#continuous-integration)
59 | - [Disabling jsdom](#disabling-jsdom)
60 | - [Snapshot Testing](#snapshot-testing)
61 | - [Editor Integration](#editor-integration)
62 | - [Developing Components in Isolation](#developing-components-in-isolation)
63 | - [Making a Progressive Web App](#making-a-progressive-web-app)
64 | - [Deployment](#deployment)
65 | - [Serving Apps with Client-Side Routing](#serving-apps-with-client-side-routing)
66 | - [Building for Relative Paths](#building-for-relative-paths)
67 | - [Azure](#azure)
68 | - [Firebase](#firebase)
69 | - [GitHub Pages](#github-pages)
70 | - [Heroku](#heroku)
71 | - [Modulus](#modulus)
72 | - [Netlify](#netlify)
73 | - [Now](#now)
74 | - [S3 and CloudFront](#s3-and-cloudfront)
75 | - [Surge](#surge)
76 | - [Advanced Configuration](#advanced-configuration)
77 | - [Troubleshooting](#troubleshooting)
78 | - [`npm start` doesn’t detect changes](#npm-start-doesnt-detect-changes)
79 | - [`npm test` hangs on macOS Sierra](#npm-test-hangs-on-macos-sierra)
80 | - [`npm run build` silently fails](#npm-run-build-silently-fails)
81 | - [`npm run build` fails on Heroku](#npm-run-build-fails-on-heroku)
82 | - [Something Missing?](#something-missing)
83 |
84 | ## Updating to New Releases
85 |
86 | Create React App is divided into two packages:
87 |
88 | * `create-react-app` is a global command-line utility that you use to create new projects.
89 | * `react-scripts` is a development dependency in the generated projects (including this one).
90 |
91 | You almost never need to update `create-react-app` itself: it delegates all the setup to `react-scripts`.
92 |
93 | When you run `create-react-app`, it always creates the project with the latest version of `react-scripts` so you’ll get all the new features and improvements in newly created apps automatically.
94 |
95 | To update an existing project to a new version of `react-scripts`, [open the changelog](https://github.com/facebookincubator/create-react-app/blob/master/CHANGELOG.md), find the version you’re currently on (check `package.json` in this folder if you’re not sure), and apply the migration instructions for the newer versions.
96 |
97 | In most cases bumping the `react-scripts` version in `package.json` and running `npm install` in this folder should be enough, but it’s good to consult the [changelog](https://github.com/facebookincubator/create-react-app/blob/master/CHANGELOG.md) for potential breaking changes.
98 |
99 | We commit to keeping the breaking changes minimal so you can upgrade `react-scripts` painlessly.
100 |
101 | ## Sending Feedback
102 |
103 | We are always open to [your feedback](https://github.com/facebookincubator/create-react-app/issues).
104 |
105 | ## Folder Structure
106 |
107 | After creation, your project should look like this:
108 |
109 | ```
110 | my-app/
111 | README.md
112 | node_modules/
113 | package.json
114 | public/
115 | index.html
116 | favicon.ico
117 | src/
118 | App.css
119 | App.js
120 | App.test.js
121 | index.css
122 | index.js
123 | logo.svg
124 | ```
125 |
126 | For the project to build, **these files must exist with exact filenames**:
127 |
128 | * `public/index.html` is the page template;
129 | * `src/index.js` is the JavaScript entry point.
130 |
131 | You can delete or rename the other files.
132 |
133 | You may create subdirectories inside `src`. For faster rebuilds, only files inside `src` are processed by Webpack.
134 | You need to **put any JS and CSS files inside `src`**, or Webpack won’t see them.
135 |
136 | Only files inside `public` can be used from `public/index.html`.
137 | Read instructions below for using assets from JavaScript and HTML.
138 |
139 | You can, however, create more top-level directories.
140 | They will not be included in the production build so you can use them for things like documentation.
141 |
142 | ## Available Scripts
143 |
144 | In the project directory, you can run:
145 |
146 | ### `npm start`
147 |
148 | Runs the app in the development mode.
149 | Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
150 |
151 | The page will reload if you make edits.
152 | You will also see any lint errors in the console.
153 |
154 | ### `npm test`
155 |
156 | Launches the test runner in the interactive watch mode.
157 | See the section about [running tests](#running-tests) for more information.
158 |
159 | ### `npm run build`
160 |
161 | Builds the app for production to the `build` folder.
162 | It correctly bundles React in production mode and optimizes the build for the best performance.
163 |
164 | The build is minified and the filenames include the hashes.
165 | Your app is ready to be deployed!
166 |
167 | See the section about [deployment](#deployment) for more information.
168 |
169 | ### `npm run eject`
170 |
171 | **Note: this is a one-way operation. Once you `eject`, you can’t go back!**
172 |
173 | 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.
174 |
175 | 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.
176 |
177 | 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.
178 |
179 | ## Supported Language Features and Polyfills
180 |
181 | This project supports a superset of the latest JavaScript standard.
182 | In addition to [ES6](https://github.com/lukehoban/es6features) syntax features, it also supports:
183 |
184 | * [Exponentiation Operator](https://github.com/rwaldron/exponentiation-operator) (ES2016).
185 | * [Async/await](https://github.com/tc39/ecmascript-asyncawait) (ES2017).
186 | * [Object Rest/Spread Properties](https://github.com/sebmarkbage/ecmascript-rest-spread) (stage 3 proposal).
187 | * [Class Fields and Static Properties](https://github.com/tc39/proposal-class-public-fields) (stage 2 proposal).
188 | * [JSX](https://facebook.github.io/react/docs/introducing-jsx.html) and [Flow](https://flowtype.org/) syntax.
189 |
190 | Learn more about [different proposal stages](https://babeljs.io/docs/plugins/#presets-stage-x-experimental-presets-).
191 |
192 | While we recommend to use experimental proposals with some caution, Facebook heavily uses these features in the product code, so we intend to provide [codemods](https://medium.com/@cpojer/effective-javascript-codemods-5a6686bb46fb) if any of these proposals change in the future.
193 |
194 | Note that **the project only includes a few ES6 [polyfills](https://en.wikipedia.org/wiki/Polyfill)**:
195 |
196 | * [`Object.assign()`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Object/assign) via [`object-assign`](https://github.com/sindresorhus/object-assign).
197 | * [`Promise`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) via [`promise`](https://github.com/then/promise).
198 | * [`fetch()`](https://developer.mozilla.org/en/docs/Web/API/Fetch_API) via [`whatwg-fetch`](https://github.com/github/fetch).
199 |
200 | If you use any other ES6+ features that need **runtime support** (such as `Array.from()` or `Symbol`), make sure you are including the appropriate polyfills manually, or that the browsers you are targeting already support them.
201 |
202 | ## Syntax Highlighting in the Editor
203 |
204 | To configure the syntax highlighting in your favorite text editor, head to the [relevant Babel documentation page](https://babeljs.io/docs/editors) and follow the instructions. Some of the most popular editors are covered.
205 |
206 | ## Displaying Lint Output in the Editor
207 |
208 | >Note: this feature is available with `react-scripts@0.2.0` and higher.
209 |
210 | Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.
211 |
212 | They are not required for linting. You should see the linter output right in your terminal as well as the browser console. However, if you prefer the lint results to appear right in your editor, there are some extra steps you can do.
213 |
214 | You would need to install an ESLint plugin for your editor first.
215 |
216 | >**A note for Atom `linter-eslint` users**
217 |
218 | >If you are using the Atom `linter-eslint` plugin, make sure that **Use global ESLint installation** option is checked:
219 |
220 | >
221 |
222 |
223 | >**For Visual Studio Code users**
224 |
225 | >VS Code ESLint plugin automatically detects Create React App's configuration file. So you do not need to create `eslintrc.json` at the root directory, except when you want to add your own rules. In that case, you should include CRA's config by adding this line:
226 |
227 | >```js
228 | {
229 | // ...
230 | "extends": "react-app"
231 | }
232 | ```
233 |
234 | Then add this block to the `package.json` file of your project:
235 |
236 | ```js
237 | {
238 | // ...
239 | "eslintConfig": {
240 | "extends": "react-app"
241 | }
242 | }
243 | ```
244 |
245 | Finally, you will need to install some packages *globally*:
246 |
247 | ```sh
248 | npm install -g eslint-config-react-app@0.3.0 eslint@3.8.1 babel-eslint@7.0.0 eslint-plugin-react@6.4.1 eslint-plugin-import@2.0.1 eslint-plugin-jsx-a11y@2.2.3 eslint-plugin-flowtype@2.21.0
249 | ```
250 |
251 | We recognize that this is suboptimal, but it is currently required due to the way we hide the ESLint dependency. The ESLint team is already [working on a solution to this](https://github.com/eslint/eslint/issues/3458) so this may become unnecessary in a couple of months.
252 |
253 | ## Debugging in the Editor
254 |
255 | **This feature is currently only supported by [Visual Studio Code](https://code.visualstudio.com) editor.**
256 |
257 | Visual Studio Code supports live-editing and debugging out of the box with Create React App. This enables you as a developer to write and debug your React code without leaving the editor, and most importantly it enables you to have a continuous development workflow, where context switching is minimal, as you don’t have to switch between tools.
258 |
259 | You would need to have the latest version of [VS Code](https://code.visualstudio.com) and VS Code [Chrome Debugger Extension](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) installed.
260 |
261 | Then add the block below to your `launch.json` file and put it inside the `.vscode` folder in your app’s root directory.
262 |
263 | ```json
264 | {
265 | "version": "0.2.0",
266 | "configurations": [{
267 | "name": "Chrome",
268 | "type": "chrome",
269 | "request": "launch",
270 | "url": "http://localhost:3000",
271 | "webRoot": "${workspaceRoot}/src",
272 | "userDataDir": "${workspaceRoot}/.vscode/chrome",
273 | "sourceMapPathOverrides": {
274 | "webpack:///src/*": "${webRoot}/*"
275 | }
276 | }]
277 | }
278 | ```
279 |
280 | Start your app by running `npm start`, and start debugging in VS Code by pressing `F5` or by clicking the green debug icon. You can now write code, set breakpoints, make changes to the code, and debug your newly modified code—all from your editor.
281 |
282 | ## Changing the Page ``
283 |
284 | You can find the source HTML file in the `public` folder of the generated project. You may edit the `` tag in it to change the title from “React App” to anything else.
285 |
286 | Note that normally you wouldn’t edit files in the `public` folder very often. For example, [adding a stylesheet](#adding-a-stylesheet) is done without touching the HTML.
287 |
288 | If you need to dynamically update the page title based on the content, you can use the browser [`document.title`](https://developer.mozilla.org/en-US/docs/Web/API/Document/title) API. For more complex scenarios when you want to change the title from React components, you can use [React Helmet](https://github.com/nfl/react-helmet), a third party library.
289 |
290 | If you use a custom server for your app in production and want to modify the title before it gets sent to the browser, you can follow advice in [this section](#generating-dynamic-meta-tags-on-the-server). Alternatively, you can pre-build each page as a static HTML file which then loads the JavaScript bundle, which is covered [here](#pre-rendering-into-static-html-files).
291 |
292 | ## Installing a Dependency
293 |
294 | The generated project includes React and ReactDOM as dependencies. It also includes a set of scripts used by Create React App as a development dependency. You may install other dependencies (for example, React Router) with `npm`:
295 |
296 | ```
297 | npm install --save
298 | ```
299 |
300 | ## Importing a Component
301 |
302 | This project setup supports ES6 modules thanks to Babel.
303 | While you can still use `require()` and `module.exports`, we encourage you to use [`import` and `export`](http://exploringjs.com/es6/ch_modules.html) instead.
304 |
305 | For example:
306 |
307 | ### `Button.js`
308 |
309 | ```js
310 | import React, { Component } from 'react';
311 |
312 | class Button extends Component {
313 | render() {
314 | // ...
315 | }
316 | }
317 |
318 | export default Button; // Don’t forget to use export default!
319 | ```
320 |
321 | ### `DangerButton.js`
322 |
323 |
324 | ```js
325 | import React, { Component } from 'react';
326 | import Button from './Button'; // Import a component from another file
327 |
328 | class DangerButton extends Component {
329 | render() {
330 | return ;
331 | }
332 | }
333 |
334 | export default DangerButton;
335 | ```
336 |
337 | Be aware of the [difference between default and named exports](http://stackoverflow.com/questions/36795819/react-native-es-6-when-should-i-use-curly-braces-for-import/36796281#36796281). It is a common source of mistakes.
338 |
339 | We suggest that you stick to using default imports and exports when a module only exports a single thing (for example, a component). That’s what you get when you use `export default Button` and `import Button from './Button'`.
340 |
341 | Named exports are useful for utility modules that export several functions. A module may have at most one default export and as many named exports as you like.
342 |
343 | Learn more about ES6 modules:
344 |
345 | * [When to use the curly braces?](http://stackoverflow.com/questions/36795819/react-native-es-6-when-should-i-use-curly-braces-for-import/36796281#36796281)
346 | * [Exploring ES6: Modules](http://exploringjs.com/es6/ch_modules.html)
347 | * [Understanding ES6: Modules](https://leanpub.com/understandinges6/read#leanpub-auto-encapsulating-code-with-modules)
348 |
349 | ## Adding a Stylesheet
350 |
351 | This project setup uses [Webpack](https://webpack.github.io/) for handling all assets. Webpack offers a custom way of “extending” the concept of `import` beyond JavaScript. To express that a JavaScript file depends on a CSS file, you need to **import the CSS from the JavaScript file**:
352 |
353 | ### `Button.css`
354 |
355 | ```css
356 | .Button {
357 | padding: 20px;
358 | }
359 | ```
360 |
361 | ### `Button.js`
362 |
363 | ```js
364 | import React, { Component } from 'react';
365 | import './Button.css'; // Tell Webpack that Button.js uses these styles
366 |
367 | class Button extends Component {
368 | render() {
369 | // You can use them as regular CSS styles
370 | return
;
371 | }
372 | }
373 | ```
374 |
375 | **This is not required for React** but many people find this feature convenient. You can read about the benefits of this approach [here](https://medium.com/seek-ui-engineering/block-element-modifying-your-javascript-components-d7f99fcab52b). However you should be aware that this makes your code less portable to other build tools and environments than Webpack.
376 |
377 | In development, expressing dependencies this way allows your styles to be reloaded on the fly as you edit them. In production, all CSS files will be concatenated into a single minified `.css` file in the build output.
378 |
379 | If you are concerned about using Webpack-specific semantics, you can put all your CSS right into `src/index.css`. It would still be imported from `src/index.js`, but you could always remove that import if you later migrate to a different build tool.
380 |
381 | ## Post-Processing CSS
382 |
383 | This project setup minifies your CSS and adds vendor prefixes to it automatically through [Autoprefixer](https://github.com/postcss/autoprefixer) so you don’t need to worry about it.
384 |
385 | For example, this:
386 |
387 | ```css
388 | .App {
389 | display: flex;
390 | flex-direction: row;
391 | align-items: center;
392 | }
393 | ```
394 |
395 | becomes this:
396 |
397 | ```css
398 | .App {
399 | display: -webkit-box;
400 | display: -ms-flexbox;
401 | display: flex;
402 | -webkit-box-orient: horizontal;
403 | -webkit-box-direction: normal;
404 | -ms-flex-direction: row;
405 | flex-direction: row;
406 | -webkit-box-align: center;
407 | -ms-flex-align: center;
408 | align-items: center;
409 | }
410 | ```
411 |
412 | If you need to disable autoprefixing for some reason, [follow this section](https://github.com/postcss/autoprefixer#disabling).
413 |
414 | ## Adding a CSS Preprocessor (Sass, Less etc.)
415 |
416 | Generally, we recommend that you don’t reuse the same CSS classes across different components. For example, instead of using a `.Button` CSS class in `` and `` components, we recommend creating a `` component with its own `.Button` styles, that both `` and `` can render (but [not inherit](https://facebook.github.io/react/docs/composition-vs-inheritance.html)).
417 |
418 | Following this rule often makes CSS preprocessors less useful, as features like mixins and nesting are replaced by component composition. You can, however, integrate a CSS preprocessor if you find it valuable. In this walkthrough, we will be using Sass, but you can also use Less, or another alternative.
419 |
420 | First, let’s install the command-line interface for Sass:
421 |
422 | ```
423 | npm install node-sass --save-dev
424 | ```
425 |
426 | Then in `package.json`, add the following lines to `scripts`:
427 |
428 | ```diff
429 | "scripts": {
430 | + "build-css": "node-sass src/ -o src/",
431 | + "watch-css": "npm run build-css && node-sass src/ -o src/ --watch",
432 | "start": "react-scripts start",
433 | "build": "react-scripts build",
434 | "test": "react-scripts test --env=jsdom",
435 | ```
436 |
437 | >Note: To use a different preprocessor, replace `build-css` and `watch-css` commands according to your preprocessor’s documentation.
438 |
439 | Now you can rename `src/App.css` to `src/App.scss` and run `npm run watch-css`. The watcher will find every Sass file in `src` subdirectories, and create a corresponding CSS file next to it, in our case overwriting `src/App.css`. Since `src/App.js` still imports `src/App.css`, the styles become a part of your application. You can now edit `src/App.scss`, and `src/App.css` will be regenerated.
440 |
441 | To share variables between Sass files, you can use Sass imports. For example, `src/App.scss` and other component style files could include `@import "./shared.scss";` with variable definitions.
442 |
443 | At this point you might want to remove all CSS files from the source control, and add `src/**/*.css` to your `.gitignore` file. It is generally a good practice to keep the build products outside of the source control.
444 |
445 | As a final step, you may find it convenient to run `watch-css` automatically with `npm start`, and run `build-css` as a part of `npm run build`. You can use the `&&` operator to execute two scripts sequentially. However, there is no cross-platform way to run two scripts in parallel, so we will install a package for this:
446 |
447 | ```
448 | npm install --save-dev npm-run-all
449 | ```
450 |
451 | Then we can change `start` and `build` scripts to include the CSS preprocessor commands:
452 |
453 | ```diff
454 | "scripts": {
455 | "build-css": "node-sass src/ -o src/",
456 | "watch-css": "npm run build-css && node-sass src/ -o src/ --watch --recursive",
457 | - "start": "react-scripts start",
458 | - "build": "react-scripts build",
459 | + "start-js": "react-scripts start",
460 | + "start": "npm-run-all -p watch-css start-js",
461 | + "build": "npm run build-css && react-scripts build",
462 | "test": "react-scripts test --env=jsdom",
463 | "eject": "react-scripts eject"
464 | }
465 | ```
466 |
467 | Now running `npm start` and `npm run build` also builds Sass files. Note that `node-sass` seems to have an [issue recognizing newly created files on some systems](https://github.com/sass/node-sass/issues/1891) so you might need to restart the watcher when you create a file until it’s resolved.
468 |
469 | ## Adding Images and Fonts
470 |
471 | With Webpack, using static assets like images and fonts works similarly to CSS.
472 |
473 | You can **`import` an image right in a JavaScript module**. This tells Webpack to include that image in the bundle. Unlike CSS imports, importing an image or a font gives you a string value. This value is the final image path you can reference in your code.
474 |
475 | Here is an example:
476 |
477 | ```js
478 | import React from 'react';
479 | import logo from './logo.png'; // Tell Webpack this JS file uses this image
480 |
481 | console.log(logo); // /logo.84287d09.png
482 |
483 | function Header() {
484 | // Import result is the URL of your image
485 | return ;
486 | }
487 |
488 | export default Header;
489 | ```
490 |
491 | This ensures that when the project is built, Webpack will correctly move the images into the build folder, and provide us with correct paths.
492 |
493 | This works in CSS too:
494 |
495 | ```css
496 | .Logo {
497 | background-image: url(./logo.png);
498 | }
499 | ```
500 |
501 | Webpack finds all relative module references in CSS (they start with `./`) and replaces them with the final paths from the compiled bundle. If you make a typo or accidentally delete an important file, you will see a compilation error, just like when you import a non-existent JavaScript module. The final filenames in the compiled bundle are generated by Webpack from content hashes. If the file content changes in the future, Webpack will give it a different name in production so you don’t need to worry about long-term caching of assets.
502 |
503 | Please be advised that this is also a custom feature of Webpack.
504 |
505 | **It is not required for React** but many people enjoy it (and React Native uses a similar mechanism for images).
506 | An alternative way of handling static assets is described in the next section.
507 |
508 | ## Using the `public` Folder
509 |
510 | >Note: this feature is available with `react-scripts@0.5.0` and higher.
511 |
512 | ### Changing the HTML
513 |
514 | The `public` folder contains the HTML file so you can tweak it, for example, to [set the page title](#changing-the-page-title).
515 | The `
886 | ```
887 |
888 | Then, on the server, you can replace `__SERVER_DATA__` with a JSON of real data right before sending the response. The client code can then read `window.SERVER_DATA` to use it. **Make sure to [sanitize the JSON before sending it to the client](https://medium.com/node-security/the-most-common-xss-vulnerability-in-react-js-applications-2bdffbcc1fa0) as it makes your app vulnerable to XSS attacks.**
889 |
890 | ## Running Tests
891 |
892 | >Note: this feature is available with `react-scripts@0.3.0` and higher.
893 | >[Read the migration guide to learn how to enable it in older projects!](https://github.com/facebookincubator/create-react-app/blob/master/CHANGELOG.md#migrating-from-023-to-030)
894 |
895 | Create React App uses [Jest](https://facebook.github.io/jest/) as its test runner. To prepare for this integration, we did a [major revamp](https://facebook.github.io/jest/blog/2016/09/01/jest-15.html) of Jest so if you heard bad things about it years ago, give it another try.
896 |
897 | Jest is a Node-based runner. This means that the tests always run in a Node environment and not in a real browser. This lets us enable fast iteration speed and prevent flakiness.
898 |
899 | While Jest provides browser globals such as `window` thanks to [jsdom](https://github.com/tmpvar/jsdom), they are only approximations of the real browser behavior. Jest is intended to be used for unit tests of your logic and your components rather than the DOM quirks.
900 |
901 | We recommend that you use a separate tool for browser end-to-end tests if you need them. They are beyond the scope of Create React App.
902 |
903 | ### Filename Conventions
904 |
905 | Jest will look for test files with any of the following popular naming conventions:
906 |
907 | * Files with `.js` suffix in `__tests__` folders.
908 | * Files with `.test.js` suffix.
909 | * Files with `.spec.js` suffix.
910 |
911 | The `.test.js` / `.spec.js` files (or the `__tests__` folders) can be located at any depth under the `src` top level folder.
912 |
913 | We recommend to put the test files (or `__tests__` folders) next to the code they are testing so that relative imports appear shorter. For example, if `App.test.js` and `App.js` are in the same folder, the test just needs to `import App from './App'` instead of a long relative path. Colocation also helps find tests more quickly in larger projects.
914 |
915 | ### Command Line Interface
916 |
917 | When you run `npm test`, Jest will launch in the watch mode. Every time you save a file, it will re-run the tests, just like `npm start` recompiles the code.
918 |
919 | The watcher includes an interactive command-line interface with the ability to run all tests, or focus on a search pattern. It is designed this way so that you can keep it open and enjoy fast re-runs. You can learn the commands from the “Watch Usage” note that the watcher prints after every run:
920 |
921 | 
922 |
923 | ### Version Control Integration
924 |
925 | By default, when you run `npm test`, Jest will only run the tests related to files changed since the last commit. This is an optimization designed to make your tests runs fast regardless of how many tests you have. However it assumes that you don’t often commit the code that doesn’t pass the tests.
926 |
927 | Jest will always explicitly mention that it only ran tests related to the files changed since the last commit. You can also press `a` in the watch mode to force Jest to run all tests.
928 |
929 | Jest will always run all tests on a [continuous integration](#continuous-integration) server or if the project is not inside a Git or Mercurial repository.
930 |
931 | ### Writing Tests
932 |
933 | To create tests, add `it()` (or `test()`) blocks with the name of the test and its code. You may optionally wrap them in `describe()` blocks for logical grouping but this is neither required nor recommended.
934 |
935 | Jest provides a built-in `expect()` global function for making assertions. A basic test could look like this:
936 |
937 | ```js
938 | import sum from './sum';
939 |
940 | it('sums numbers', () => {
941 | expect(sum(1, 2)).toEqual(3);
942 | expect(sum(2, 2)).toEqual(4);
943 | });
944 | ```
945 |
946 | All `expect()` matchers supported by Jest are [extensively documented here](http://facebook.github.io/jest/docs/expect.html).
947 | You can also use [`jest.fn()` and `expect(fn).toBeCalled()`](http://facebook.github.io/jest/docs/expect.html#tohavebeencalled) to create “spies” or mock functions.
948 |
949 | ### Testing Components
950 |
951 | There is a broad spectrum of component testing techniques. They range from a “smoke test” verifying that a component renders without throwing, to shallow rendering and testing some of the output, to full rendering and testing component lifecycle and state changes.
952 |
953 | Different projects choose different testing tradeoffs based on how often components change, and how much logic they contain. If you haven’t decided on a testing strategy yet, we recommend that you start with creating simple smoke tests for your components:
954 |
955 | ```js
956 | import React from 'react';
957 | import ReactDOM from 'react-dom';
958 | import App from './App';
959 |
960 | it('renders without crashing', () => {
961 | const div = document.createElement('div');
962 | ReactDOM.render( , div);
963 | });
964 | ```
965 |
966 | This test mounts a component and makes sure that it didn’t throw during rendering. Tests like this provide a lot value with very little effort so they are great as a starting point, and this is the test you will find in `src/App.test.js`.
967 |
968 | When you encounter bugs caused by changing components, you will gain a deeper insight into which parts of them are worth testing in your application. This might be a good time to introduce more specific tests asserting specific expected output or behavior.
969 |
970 | If you’d like to test components in isolation from the child components they render, we recommend using [`shallow()` rendering API](http://airbnb.io/enzyme/docs/api/shallow.html) from [Enzyme](http://airbnb.io/enzyme/). You can write a smoke test with it too:
971 |
972 | ```sh
973 | npm install --save-dev enzyme react-addons-test-utils
974 | ```
975 |
976 | ```js
977 | import React from 'react';
978 | import { shallow } from 'enzyme';
979 | import App from './App';
980 |
981 | it('renders without crashing', () => {
982 | shallow( );
983 | });
984 | ```
985 |
986 | Unlike the previous smoke test using `ReactDOM.render()`, this test only renders `` and doesn’t go deeper. For example, even if `` itself renders a `` that throws, this test will pass. Shallow rendering is great for isolated unit tests, but you may still want to create some full rendering tests to ensure the components integrate correctly. Enzyme supports [full rendering with `mount()`](http://airbnb.io/enzyme/docs/api/mount.html), and you can also use it for testing state changes and component lifecycle.
987 |
988 | You can read the [Enzyme documentation](http://airbnb.io/enzyme/) for more testing techniques. Enzyme documentation uses Chai and Sinon for assertions but you don’t have to use them because Jest provides built-in `expect()` and `jest.fn()` for spies.
989 |
990 | Here is an example from Enzyme documentation that asserts specific output, rewritten to use Jest matchers:
991 |
992 | ```js
993 | import React from 'react';
994 | import { shallow } from 'enzyme';
995 | import App from './App';
996 |
997 | it('renders welcome message', () => {
998 | const wrapper = shallow( );
999 | const welcome = Welcome to React ;
1000 | // expect(wrapper.contains(welcome)).to.equal(true);
1001 | expect(wrapper.contains(welcome)).toEqual(true);
1002 | });
1003 | ```
1004 |
1005 | All Jest matchers are [extensively documented here](http://facebook.github.io/jest/docs/expect.html).
1006 | Nevertheless you can use a third-party assertion library like [Chai](http://chaijs.com/) if you want to, as described below.
1007 |
1008 | Additionally, you might find [jest-enzyme](https://github.com/blainekasten/enzyme-matchers) helpful to simplify your tests with readable matchers. The above `contains` code can be written simpler with jest-enzyme.
1009 |
1010 | ```js
1011 | expect(wrapper).toContainReact(welcome)
1012 | ```
1013 |
1014 | To setup jest-enzyme with Create React App, follow the instructions for [initializing your test environment](#initializing-test-environment) to import `jest-enzyme`.
1015 |
1016 | ```sh
1017 | npm install --save-dev jest-enzyme
1018 | ```
1019 |
1020 | ```js
1021 | // src/setupTests.js
1022 | import 'jest-enzyme';
1023 | ```
1024 |
1025 |
1026 | ### Using Third Party Assertion Libraries
1027 |
1028 | We recommend that you use `expect()` for assertions and `jest.fn()` for spies. If you are having issues with them please [file those against Jest](https://github.com/facebook/jest/issues/new), and we’ll fix them. We intend to keep making them better for React, supporting, for example, [pretty-printing React elements as JSX](https://github.com/facebook/jest/pull/1566).
1029 |
1030 | However, if you are used to other libraries, such as [Chai](http://chaijs.com/) and [Sinon](http://sinonjs.org/), or if you have existing code using them that you’d like to port over, you can import them normally like this:
1031 |
1032 | ```js
1033 | import sinon from 'sinon';
1034 | import { expect } from 'chai';
1035 | ```
1036 |
1037 | and then use them in your tests like you normally do.
1038 |
1039 | ### Initializing Test Environment
1040 |
1041 | >Note: this feature is available with `react-scripts@0.4.0` and higher.
1042 |
1043 | If your app uses a browser API that you need to mock in your tests or if you just need a global setup before running your tests, add a `src/setupTests.js` to your project. It will be automatically executed before running your tests.
1044 |
1045 | For example:
1046 |
1047 | #### `src/setupTests.js`
1048 | ```js
1049 | const localStorageMock = {
1050 | getItem: jest.fn(),
1051 | setItem: jest.fn(),
1052 | clear: jest.fn()
1053 | };
1054 | global.localStorage = localStorageMock
1055 | ```
1056 |
1057 | ### Focusing and Excluding Tests
1058 |
1059 | You can replace `it()` with `xit()` to temporarily exclude a test from being executed.
1060 | Similarly, `fit()` lets you focus on a specific test without running any other tests.
1061 |
1062 | ### Coverage Reporting
1063 |
1064 | Jest has an integrated coverage reporter that works well with ES6 and requires no configuration.
1065 | Run `npm test -- --coverage` (note extra `--` in the middle) to include a coverage report like this:
1066 |
1067 | 
1068 |
1069 | Note that tests run much slower with coverage so it is recommended to run it separately from your normal workflow.
1070 |
1071 | ### Continuous Integration
1072 |
1073 | By default `npm test` runs the watcher with interactive CLI. However, you can force it to run tests once and finish the process by setting an environment variable called `CI`.
1074 |
1075 | When creating a build of your application with `npm run build` linter warnings are not checked by default. Like `npm test`, you can force the build to perform a linter warning check by setting the environment variable `CI`. If any warnings are encountered then the build fails.
1076 |
1077 | Popular CI servers already set the environment variable `CI` by default but you can do this yourself too:
1078 |
1079 | ### On CI servers
1080 | #### Travis CI
1081 |
1082 | 1. Following the [Travis Getting started](https://docs.travis-ci.com/user/getting-started/) guide for syncing your GitHub repository with Travis. You may need to initialize some settings manually in your [profile](https://travis-ci.org/profile) page.
1083 | 1. Add a `.travis.yml` file to your git repository.
1084 | ```
1085 | language: node_js
1086 | node_js:
1087 | - 4
1088 | - 6
1089 | cache:
1090 | directories:
1091 | - node_modules
1092 | script:
1093 | - npm test
1094 | - npm run build
1095 | ```
1096 | 1. Trigger your first build with a git push.
1097 | 1. [Customize your Travis CI Build](https://docs.travis-ci.com/user/customizing-the-build/) if needed.
1098 |
1099 | ### On your own environment
1100 | ##### Windows (cmd.exe)
1101 |
1102 | ```cmd
1103 | set CI=true&&npm test
1104 | ```
1105 |
1106 | ```cmd
1107 | set CI=true&&npm run build
1108 | ```
1109 |
1110 | (Note: the lack of whitespace is intentional.)
1111 |
1112 | ##### Linux, macOS (Bash)
1113 |
1114 | ```bash
1115 | CI=true npm test
1116 | ```
1117 |
1118 | ```bash
1119 | CI=true npm run build
1120 | ```
1121 |
1122 | The test command will force Jest to run tests once instead of launching the watcher.
1123 |
1124 | > If you find yourself doing this often in development, please [file an issue](https://github.com/facebookincubator/create-react-app/issues/new) to tell us about your use case because we want to make watcher the best experience and are open to changing how it works to accommodate more workflows.
1125 |
1126 | The build command will check for linter warnings and fail if any are found.
1127 |
1128 | ### Disabling jsdom
1129 |
1130 | By default, the `package.json` of the generated project looks like this:
1131 |
1132 | ```js
1133 | // ...
1134 | "scripts": {
1135 | // ...
1136 | "test": "react-scripts test --env=jsdom"
1137 | }
1138 | ```
1139 |
1140 | If you know that none of your tests depend on [jsdom](https://github.com/tmpvar/jsdom), you can safely remove `--env=jsdom`, and your tests will run faster.
1141 | To help you make up your mind, here is a list of APIs that **need jsdom**:
1142 |
1143 | * Any browser globals like `window` and `document`
1144 | * [`ReactDOM.render()`](https://facebook.github.io/react/docs/top-level-api.html#reactdom.render)
1145 | * [`TestUtils.renderIntoDocument()`](https://facebook.github.io/react/docs/test-utils.html#renderintodocument) ([a shortcut](https://github.com/facebook/react/blob/34761cf9a252964abfaab6faf74d473ad95d1f21/src/test/ReactTestUtils.js#L83-L91) for the above)
1146 | * [`mount()`](http://airbnb.io/enzyme/docs/api/mount.html) in [Enzyme](http://airbnb.io/enzyme/index.html)
1147 |
1148 | In contrast, **jsdom is not needed** for the following APIs:
1149 |
1150 | * [`TestUtils.createRenderer()`](https://facebook.github.io/react/docs/test-utils.html#shallow-rendering) (shallow rendering)
1151 | * [`shallow()`](http://airbnb.io/enzyme/docs/api/shallow.html) in [Enzyme](http://airbnb.io/enzyme/index.html)
1152 |
1153 | Finally, jsdom is also not needed for [snapshot testing](http://facebook.github.io/jest/blog/2016/07/27/jest-14.html).
1154 |
1155 | ### Snapshot Testing
1156 |
1157 | Snapshot testing is a feature of Jest that automatically generates text snapshots of your components and saves them on the disk so if the UI output changes, you get notified without manually writing any assertions on the component output. [Read more about snapshot testing.](http://facebook.github.io/jest/blog/2016/07/27/jest-14.html)
1158 |
1159 | ### Editor Integration
1160 |
1161 | If you use [Visual Studio Code](https://code.visualstudio.com), there is a [Jest extension](https://github.com/orta/vscode-jest) which works with Create React App out of the box. This provides a lot of IDE-like features while using a text editor: showing the status of a test run with potential fail messages inline, starting and stopping the watcher automatically, and offering one-click snapshot updates.
1162 |
1163 | 
1164 |
1165 | ## Developing Components in Isolation
1166 |
1167 | Usually, in an app, you have a lot of UI components, and each of them has many different states.
1168 | For an example, a simple button component could have following states:
1169 |
1170 | * With a text label.
1171 | * With an emoji.
1172 | * In the disabled mode.
1173 |
1174 | Usually, it’s hard to see these states without running a sample app or some examples.
1175 |
1176 | Create React App doesn’t include any tools for this by default, but you can easily add [React Storybook](https://github.com/kadirahq/react-storybook) to your project. **It is a third-party tool that lets you develop components and see all their states in isolation from your app**.
1177 |
1178 | 
1179 |
1180 | You can also deploy your Storybook as a static app. This way, everyone in your team can view and review different states of UI components without starting a backend server or creating an account in your app.
1181 |
1182 | **Here’s how to setup your app with Storybook:**
1183 |
1184 | First, install the following npm package globally:
1185 |
1186 | ```sh
1187 | npm install -g getstorybook
1188 | ```
1189 |
1190 | Then, run the following command inside your app’s directory:
1191 |
1192 | ```sh
1193 | getstorybook
1194 | ```
1195 |
1196 | After that, follow the instructions on the screen.
1197 |
1198 | Learn more about React Storybook:
1199 |
1200 | * Screencast: [Getting Started with React Storybook](https://egghead.io/lessons/react-getting-started-with-react-storybook)
1201 | * [GitHub Repo](https://github.com/kadirahq/react-storybook)
1202 | * [Documentation](https://getstorybook.io/docs)
1203 | * [Snapshot Testing](https://github.com/kadirahq/storyshots) with React Storybook
1204 |
1205 | ## Making a Progressive Web App
1206 |
1207 | You can turn your React app into a [Progressive Web App](https://developers.google.com/web/progressive-web-apps/) by following the steps in [this repository](https://github.com/jeffposnick/create-react-pwa).
1208 |
1209 | ## Deployment
1210 |
1211 | `npm run build` creates a `build` directory with a production build of your app. Set up your favourite HTTP server so that a visitor to your site is served `index.html`, and requests to static paths like `/static/js/main..js` are served with the contents of the `/static/js/main..js` file. For example, Python contains a built-in HTTP server that can serve static files:
1212 |
1213 | ```sh
1214 | cd build
1215 | python -m SimpleHTTPServer 9000
1216 | ```
1217 |
1218 | If you’re using [Node](https://nodejs.org/) and [Express](http://expressjs.com/) as a server, it might look like this:
1219 |
1220 | ```javascript
1221 | const express = require('express');
1222 | const path = require('path');
1223 | const app = express();
1224 |
1225 | app.use(express.static('./build'));
1226 |
1227 | app.get('/', function (req, res) {
1228 | res.sendFile(path.join(__dirname, './build', 'index.html'));
1229 | });
1230 |
1231 | app.listen(9000);
1232 | ```
1233 |
1234 | Create React App is not opinionated about your choice of web server. Any static file server will do. The `build` folder with static assets is the only output produced by Create React App.
1235 |
1236 | However this is not quite enough if you use client-side routing. Read the next section if you want to support URLs like `/todos/42` in your single-page app.
1237 |
1238 | ### Serving Apps with Client-Side Routing
1239 |
1240 | If you use routers that use the HTML5 [`pushState` history API](https://developer.mozilla.org/en-US/docs/Web/API/History_API#Adding_and_modifying_history_entries) under the hood (for example, [React Router](https://github.com/ReactTraining/react-router) with `browserHistory`), many static file servers will fail. For example, if you used React Router with a route for `/todos/42`, the development server will respond to `localhost:3000/todos/42` properly, but an Express serving a production build as above will not.
1241 |
1242 | This is because when there is a fresh page load for a `/todos/42`, the server looks for the file `build/todos/42` and does not find it. The server needs to be configured to respond to a request to `/todos/42` by serving `index.html`. For example, we can amend our Express example above to serve `index.html` for any unknown paths:
1243 |
1244 | ```diff
1245 | app.use(express.static('./build'));
1246 |
1247 | -app.get('/', function (req, res) {
1248 | +app.get('/*', function (req, res) {
1249 | res.sendFile(path.join(__dirname, './build', 'index.html'));
1250 | });
1251 | ```
1252 |
1253 | Now requests to `/todos/42` will be handled correctly both in development and in production.
1254 |
1255 | ### Building for Relative Paths
1256 |
1257 | By default, Create React App produces a build assuming your app is hosted at the server root.
1258 | To override this, specify the `homepage` in your `package.json`, for example:
1259 |
1260 | ```js
1261 | "homepage": "http://mywebsite.com/relativepath",
1262 | ```
1263 |
1264 | This will let Create React App correctly infer the root path to use in the generated HTML file.
1265 |
1266 | #### Serving the Same Build from Different Paths
1267 |
1268 | >Note: this feature is available with `react-scripts@0.9.0` and higher.
1269 |
1270 | If you are not using the HTML5 `pushState` history API or not using client-side routing at all, it is unnecessary to specify the URL from which your app will be served. Instead, you can put this in your `package.json`:
1271 |
1272 | ```js
1273 | "homepage": ".",
1274 | ```
1275 |
1276 | This will make sure that all the asset paths are relative to `index.html`. You will then be able to move your app from `http://mywebsite.com` to `http://mywebsite.com/relativepath` or even `http://mywebsite.com/relative/path` without having to rebuild it.
1277 |
1278 | ### Azure
1279 |
1280 | See [this](https://medium.com/@to_pe/deploying-create-react-app-on-microsoft-azure-c0f6686a4321) blog post on how to deploy your React app to [Microsoft Azure](https://azure.microsoft.com/).
1281 |
1282 | ### Firebase
1283 |
1284 | Install the Firebase CLI if you haven’t already by running `npm install -g firebase-tools`. Sign up for a [Firebase account](https://console.firebase.google.com/) and create a new project. Run `firebase login` and login with your previous created Firebase account.
1285 |
1286 | Then run the `firebase init` command from your project’s root. You need to choose the **Hosting: Configure and deploy Firebase Hosting sites** and choose the Firebase project you created in the previous step. You will need to agree with `database.rules.json` being created, choose `build` as the public directory, and also agree to **Configure as a single-page app** by replying with `y`.
1287 |
1288 | ```sh
1289 | === Project Setup
1290 |
1291 | First, let's associate this project directory with a Firebase project.
1292 | You can create multiple project aliases by running firebase use --add,
1293 | but for now we'll just set up a default project.
1294 |
1295 | ? What Firebase project do you want to associate as default? Example app (example-app-fd690)
1296 |
1297 | === Database Setup
1298 |
1299 | Firebase Realtime Database Rules allow you to define how your data should be
1300 | structured and when your data can be read from and written to.
1301 |
1302 | ? What file should be used for Database Rules? database.rules.json
1303 | ✔ Database Rules for example-app-fd690 have been downloaded to database.rules.json.
1304 | Future modifications to database.rules.json will update Database Rules when you run
1305 | firebase deploy.
1306 |
1307 | === Hosting Setup
1308 |
1309 | Your public directory is the folder (relative to your project directory) that
1310 | will contain Hosting assets to uploaded with firebase deploy. If you
1311 | have a build process for your assets, use your build's output directory.
1312 |
1313 | ? What do you want to use as your public directory? build
1314 | ? Configure as a single-page app (rewrite all urls to /index.html)? Yes
1315 | ✔ Wrote build/index.html
1316 |
1317 | i Writing configuration info to firebase.json...
1318 | i Writing project information to .firebaserc...
1319 |
1320 | ✔ Firebase initialization complete!
1321 | ```
1322 |
1323 | Now, after you create a production build with `npm run build`, you can deploy it by running `firebase deploy`.
1324 |
1325 | ```sh
1326 | === Deploying to 'example-app-fd690'...
1327 |
1328 | i deploying database, hosting
1329 | ✔ database: rules ready to deploy.
1330 | i hosting: preparing build directory for upload...
1331 | Uploading: [============================== ] 75%✔ hosting: build folder uploaded successfully
1332 | ✔ hosting: 8 files uploaded successfully
1333 | i starting release process (may take several minutes)...
1334 |
1335 | ✔ Deploy complete!
1336 |
1337 | Project Console: https://console.firebase.google.com/project/example-app-fd690/overview
1338 | Hosting URL: https://example-app-fd690.firebaseapp.com
1339 | ```
1340 |
1341 | For more information see [Add Firebase to your JavaScript Project](https://firebase.google.com/docs/web/setup).
1342 |
1343 | ### GitHub Pages
1344 |
1345 | >Note: this feature is available with `react-scripts@0.2.0` and higher.
1346 |
1347 | #### Step 1: Add `homepage` to `package.json`
1348 |
1349 | **The step below is important!**
1350 | **If you skip it, your app will not deploy correctly.**
1351 |
1352 | Open your `package.json` and add a `homepage` field:
1353 |
1354 | ```js
1355 | "homepage": "https://myusername.github.io/my-app",
1356 | ```
1357 |
1358 | Create React App uses the `homepage` field to determine the root URL in the built HTML file.
1359 |
1360 | #### Step 2: Install `gh-pages` and add `deploy` to `scripts` in `package.json`
1361 |
1362 | Now, whenever you run `npm run build`, you will see a cheat sheet with instructions on how to deploy to GitHub Pages.
1363 |
1364 | To publish it at [https://myusername.github.io/my-app](https://myusername.github.io/my-app), run:
1365 |
1366 | ```sh
1367 | npm install --save-dev gh-pages
1368 | ```
1369 |
1370 | Add the following scripts in your `package.json`:
1371 |
1372 | ```js
1373 | // ...
1374 | "scripts": {
1375 | // ...
1376 | "predeploy": "npm run build",
1377 | "deploy": "gh-pages -d build"
1378 | }
1379 | ```
1380 |
1381 | The `predeploy` script will run automatically before `deploy` is run.
1382 |
1383 | #### Step 3: Deploy the site by running `npm run deploy`
1384 |
1385 | Then run:
1386 |
1387 | ```sh
1388 | npm run deploy
1389 | ```
1390 |
1391 | #### Step 4: Ensure your project’s settings use `gh-pages`
1392 |
1393 | Finally, make sure **GitHub Pages** option in your GitHub project settings is set to use the `gh-pages` branch:
1394 |
1395 |
1396 |
1397 | #### Step 5: Optionally, configure the domain
1398 |
1399 | You can configure a custom domain with GitHub Pages by adding a `CNAME` file to the `public/` folder.
1400 |
1401 | #### Notes on client-side routing
1402 |
1403 | GitHub Pages doesn’t support routers that use the HTML5 `pushState` history API under the hood (for example, React Router using `browserHistory`). This is because when there is a fresh page load for a url like `http://user.github.io/todomvc/todos/42`, where `/todos/42` is a frontend route, the GitHub Pages server returns 404 because it knows nothing of `/todos/42`. If you want to add a router to a project hosted on GitHub Pages, here are a couple of solutions:
1404 |
1405 | * You could switch from using HTML5 history API to routing with hashes. If you use React Router, you can switch to `hashHistory` for this effect, but the URL will be longer and more verbose (for example, `http://user.github.io/todomvc/#/todos/42?_k=yknaj`). [Read more](https://github.com/reactjs/react-router/blob/master/docs/guides/Histories.md#histories) about different history implementations in React Router.
1406 | * Alternatively, you can use a trick to teach GitHub Pages to handle 404 by redirecting to your `index.html` page with a special redirect parameter. You would need to add a `404.html` file with the redirection code to the `build` folder before deploying your project, and you’ll need to add code handling the redirect parameter to `index.html`. You can find a detailed explanation of this technique [in this guide](https://github.com/rafrex/spa-github-pages).
1407 |
1408 | ### Heroku
1409 |
1410 | Use the [Heroku Buildpack for Create React App](https://github.com/mars/create-react-app-buildpack).
1411 | You can find instructions in [Deploying React with Zero Configuration](https://blog.heroku.com/deploying-react-with-zero-configuration).
1412 |
1413 | #### Resolving Heroku Deployment Errors
1414 |
1415 | Sometimes `npm run build` works locally but fails during deploy via Heroku. Following are the most common cases.
1416 |
1417 | ##### "Module not found: Error: Cannot resolve 'file' or 'directory'"
1418 |
1419 | If you get something like this:
1420 |
1421 | ```
1422 | remote: Failed to create a production build. Reason:
1423 | remote: Module not found: Error: Cannot resolve 'file' or 'directory'
1424 | MyDirectory in /tmp/build_1234/src
1425 | ```
1426 |
1427 | It means you need to ensure that the lettercase of the file or directory you `import` matches the one you see on your filesystem or on GitHub.
1428 |
1429 | This is important because Linux (the operating system used by Heroku) is case sensitive. So `MyDirectory` and `mydirectory` are two distinct directories and thus, even though the project builds locally, the difference in case breaks the `import` statements on Heroku remotes.
1430 |
1431 | ##### "Could not find a required file."
1432 |
1433 | If you exclude or ignore necessary files from the package you will see a error similar this one:
1434 |
1435 | ```
1436 | remote: Could not find a required file.
1437 | remote: Name: `index.html`
1438 | remote: Searched in: /tmp/build_a2875fc163b209225122d68916f1d4df/public
1439 | remote:
1440 | remote: npm ERR! Linux 3.13.0-105-generic
1441 | remote: npm ERR! argv "/tmp/build_a2875fc163b209225122d68916f1d4df/.heroku/node/bin/node" "/tmp/build_a2875fc163b209225122d68916f1d4df/.heroku/node/bin/npm" "run" "build"
1442 | ```
1443 |
1444 | In this case, ensure that the file is there with the proper lettercase and that’s not ignored on your local `.gitignore` or `~/.gitignore_global`.
1445 |
1446 | ### Modulus
1447 |
1448 | See the [Modulus blog post](http://blog.modulus.io/deploying-react-apps-on-modulus) on how to deploy your react app to Modulus.
1449 |
1450 | ## Netlify
1451 |
1452 | **To do a manual deploy to Netlify’s CDN:**
1453 |
1454 | ```sh
1455 | npm install netlify-cli
1456 | netlify deploy
1457 | ```
1458 |
1459 | Choose `build` as the path to deploy.
1460 |
1461 | **To setup continuous delivery:**
1462 |
1463 | With this setup Netlify will build and deploy when you push to git or open a pull request:
1464 |
1465 | 1. [Start a new netlify project](https://app.netlify.com/signup)
1466 | 2. Pick your Git hosting service and select your repository
1467 | 3. Click `Build your site`
1468 |
1469 | **Support for client-side routing:**
1470 |
1471 | To support `pushState`, make sure to create a `public/_redirects` file with the following rewrite rules:
1472 |
1473 | ```
1474 | /* /index.html 200
1475 | ```
1476 |
1477 | When you build the project, Create React App will place the `public` folder contents into the build output.
1478 |
1479 | ### Now
1480 |
1481 | See [this example](https://github.com/xkawi/create-react-app-now) for a zero-configuration single-command deployment with [now](https://zeit.co/now).
1482 |
1483 | ### S3 and CloudFront
1484 |
1485 | See this [blog post](https://medium.com/@omgwtfmarc/deploying-create-react-app-to-s3-or-cloudfront-48dae4ce0af) on how to deploy your React app to Amazon Web Services [S3](https://aws.amazon.com/s3) and [CloudFront](https://aws.amazon.com/cloudfront/).
1486 |
1487 | ### Surge
1488 |
1489 | Install the Surge CLI if you haven’t already by running `npm install -g surge`. Run the `surge` command and log in you or create a new account. You just need to specify the *build* folder and your custom domain, and you are done.
1490 |
1491 | ```sh
1492 | email: email@domain.com
1493 | password: ********
1494 | project path: /path/to/project/build
1495 | size: 7 files, 1.8 MB
1496 | domain: create-react-app.surge.sh
1497 | upload: [====================] 100%, eta: 0.0s
1498 | propagate on CDN: [====================] 100%
1499 | plan: Free
1500 | users: email@domain.com
1501 | IP Address: X.X.X.X
1502 |
1503 | Success! Project is published and running at create-react-app.surge.sh
1504 | ```
1505 |
1506 | Note that in order to support routers that use HTML5 `pushState` API, you may want to rename the `index.html` in your build folder to `200.html` before deploying to Surge. This [ensures that every URL falls back to that file](https://surge.sh/help/adding-a-200-page-for-client-side-routing).
1507 |
1508 | ## Advanced Configuration
1509 |
1510 | You can adjust various development and production settings by setting environment variables in your shell or with [.env](#adding-development-environment-variables-in-env).
1511 |
1512 | Variable | Development | Production | Usage
1513 | :--- | :---: | :---: | :---
1514 | BROWSER | :white_check_mark: | :x: | By default, Create React App will open the default system browser, favoring Chrome on macOS. Specify a [browser](https://github.com/sindresorhus/opn#app) to override this behavior, or set it to `none` to disable it completely.
1515 | HOST | :white_check_mark: | :x: | By default, the development web server binds to `localhost`. You may use this variable to specify a different host.
1516 | PORT | :white_check_mark: | :x: | By default, the development web server will attempt to listen on port 3000 or prompt you to attempt the next available port. You may use this variable to specify a different port.
1517 | HTTPS | :white_check_mark: | :x: | When set to `true`, Create React App will run the development server in `https` mode.
1518 | PUBLIC_URL | :x: | :white_check_mark: | Create React App assumes your application is hosted at the serving web server's root or a subpath as specified in [`package.json` (`homepage`)](#building-for-relative-paths). Normally, Create React App ignores the hostname. You may use this variable to force assets to be referenced verbatim to the url you provide (hostname included). This may be particularly useful when using a CDN to host your application.
1519 | CI | :large_orange_diamond: | :white_check_mark: | When set to `true`, Create React App treats warnings as failures in the build. It also makes the test runner non-watching. Most CIs set this flag by default.
1520 |
1521 | ## Troubleshooting
1522 |
1523 | ### `npm start` doesn’t detect changes
1524 |
1525 | When you save a file while `npm start` is running, the browser should refresh with the updated code.
1526 | If this doesn’t happen, try one of the following workarounds:
1527 |
1528 | * If your project is in a Dropbox folder, try moving it out.
1529 | * If the watcher doesn’t see a file called `index.js` and you’re referencing it by the folder name, you [need to restart the watcher](https://github.com/facebookincubator/create-react-app/issues/1164) due to a Webpack bug.
1530 | * Some editors like Vim and IntelliJ have a “safe write” feature that currently breaks the watcher. You will need to disable it. Follow the instructions in [“Working with editors supporting safe write”](https://webpack.github.io/docs/webpack-dev-server.html#working-with-editors-ides-supporting-safe-write).
1531 | * If your project path contains parentheses, try moving the project to a path without them. This is caused by a [Webpack watcher bug](https://github.com/webpack/watchpack/issues/42).
1532 | * On Linux and macOS, you might need to [tweak system settings](https://webpack.github.io/docs/troubleshooting.html#not-enough-watchers) to allow more watchers.
1533 | * If the project runs inside a virtual machine such as (a Vagrant provisioned) VirtualBox, run `npm install --save-dev cross-env` in its root folder and then replace `"react-scripts start"` in the `scripts` section of its `package.json` with `"cross-env CHOKIDAR_USEPOLLING=true react-scripts start"`. This ensures that the next time you run `npm start`, the watcher uses the polling mode, as necessary inside a VM.
1534 |
1535 | If none of these solutions help please leave a comment [in this thread](https://github.com/facebookincubator/create-react-app/issues/659).
1536 |
1537 | ### `npm test` hangs on macOS Sierra
1538 |
1539 | If you run `npm test` and the console gets stuck after printing `react-scripts test --env=jsdom` to the console there might be a problem with your [Watchman](https://facebook.github.io/watchman/) installation as described in [facebookincubator/create-react-app#713](https://github.com/facebookincubator/create-react-app/issues/713).
1540 |
1541 | We recommend deleting `node_modules` in your project and running `npm install` (or `yarn` if you use it) first. If it doesn't help, you can try one of the numerous workarounds mentioned in these issues:
1542 |
1543 | * [facebook/jest#1767](https://github.com/facebook/jest/issues/1767)
1544 | * [facebook/watchman#358](https://github.com/facebook/watchman/issues/358)
1545 | * [ember-cli/ember-cli#6259](https://github.com/ember-cli/ember-cli/issues/6259)
1546 |
1547 | It is reported that installing Watchman 4.7.0 or newer fixes the issue. If you use [Homebrew](http://brew.sh/), you can run these commands to update it:
1548 |
1549 | ```
1550 | watchman shutdown-server
1551 | brew update
1552 | brew reinstall watchman
1553 | ```
1554 |
1555 | You can find [other installation methods](https://facebook.github.io/watchman/docs/install.html#build-install) on the Watchman documentation page.
1556 |
1557 | If this still doesn’t help, try running `launchctl unload -F ~/Library/LaunchAgents/com.github.facebook.watchman.plist`.
1558 |
1559 | There are also reports that *uninstalling* Watchman fixes the issue. So if nothing else helps, remove it from your system and try again.
1560 |
1561 | ### `npm run build` silently fails
1562 |
1563 | It is reported that `npm run build` can fail on machines with no swap space, which is common in cloud environments. If [the symptoms are matching](https://github.com/facebookincubator/create-react-app/issues/1133#issuecomment-264612171), consider adding some swap space to the machine you’re building on, or build the project locally.
1564 |
1565 | ### `npm run build` fails on Heroku
1566 |
1567 | This may be a problem with case sensitive filenames.
1568 | Please refer to [this section](#resolving-heroku-deployment-errors).
1569 |
1570 | ## Something Missing?
1571 |
1572 | If you have ideas for more “How To” recipes that should be on this page, [let us know](https://github.com/facebookincubator/create-react-app/issues) or [contribute some!](https://github.com/facebookincubator/create-react-app/edit/master/packages/react-scripts/template/README.md)
1573 |
--------------------------------------------------------------------------------
/08-switch/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "beta7",
3 | "version": "0.0.1",
4 | "private": true,
5 | "devDependencies": {
6 | "react-scripts": "0.9.3"
7 | },
8 | "dependencies": {
9 | "react": "^15.4.2",
10 | "react-dom": "^15.4.2"
11 | },
12 | "scripts": {
13 | "start": "react-scripts start",
14 | "build": "react-scripts build",
15 | "test": "react-scripts test --env=jsdom",
16 | "eject": "react-scripts eject"
17 | }
18 | }
19 |
--------------------------------------------------------------------------------
/08-switch/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/gpltaylor/react-router-workshop/19d1437833dfc7d806c8e54a3a8f7db756a7311a/08-switch/public/favicon.ico
--------------------------------------------------------------------------------
/08-switch/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
16 | React App
17 |
18 |
19 |
20 |
30 |
31 |
32 |
--------------------------------------------------------------------------------
/08-switch/src/App.css:
--------------------------------------------------------------------------------
1 | .App {
2 | text-align: center;
3 | }
4 |
5 | .App-logo {
6 | animation: App-logo-spin infinite 20s linear;
7 | height: 80px;
8 | }
9 |
10 | .App-header {
11 | background-color: #222;
12 | height: 150px;
13 | padding: 20px;
14 | color: white;
15 | }
16 |
17 | .App-intro {
18 | font-size: large;
19 | }
20 |
21 | @keyframes App-logo-spin {
22 | from { transform: rotate(0deg); }
23 | to { transform: rotate(360deg); }
24 | }
25 |
--------------------------------------------------------------------------------
/08-switch/src/App.js:
--------------------------------------------------------------------------------
1 | import React, { Component } from 'react';
2 | import logo from './logo.svg';
3 | import './App.css';
4 | import Navigation from "./navigation";
5 |
6 | import {
7 | BrowserRouter as Router,
8 | Route,
9 | Switch
10 | } from 'react-router-dom';
11 |
12 | var Home = () => (
13 | To get started, edit src/App.js
and save to reload.
14 | )
15 |
16 | class AboutUs extends React.Component {
17 | constructor(props) {
18 | super(props);
19 | }
20 | componentDidMount() {
21 | alert("Costly AJAX call");
22 | }
23 |
24 | render() {
25 | return About {this.props.match.params.username || "us"}
;
26 | }
27 | }
28 |
29 | var AccountDetails = ({match}) => (
30 | Hello, {match.params.username}
31 | )
32 |
33 | var NotFound = ({match}) => (
34 | Sorry but the page {match.url} was not found
35 | )
36 |
37 | class App extends Component {
38 | render() {
39 | return (
40 |
41 |
42 |
43 |
44 |
React Router Beta 7
45 |
An Introduction to Switch
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 | );
60 | }
61 | }
62 |
63 | export default App;
64 |
--------------------------------------------------------------------------------
/08-switch/src/App.test.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import App from './App';
4 |
5 | it('renders without crashing', () => {
6 | const div = document.createElement('div');
7 | ReactDOM.render( , div);
8 | });
9 |
--------------------------------------------------------------------------------
/08-switch/src/index.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin: 0;
3 | padding: 0;
4 | font-family: sans-serif;
5 | }
6 |
7 | ul li {
8 | list-style-type: none;
9 | display: inline;
10 | }
11 |
12 | li+li:before
13 | {
14 | content: ' | ';
15 | }
--------------------------------------------------------------------------------
/08-switch/src/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import App from './App';
4 | import './index.css';
5 |
6 | ReactDOM.render(
7 | ,
8 | document.getElementById('root')
9 | );
10 |
--------------------------------------------------------------------------------
/08-switch/src/logo.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/08-switch/src/navigation.js:
--------------------------------------------------------------------------------
1 | import React from "react";
2 | import Link from 'react-router-dom/Link';
3 |
4 | var Navigation = () => {
5 | return
6 |
7 | Home
8 | About
9 | User-About
10 | Bob
11 | Missing
12 |
13 |
14 | }
15 |
16 | export default Navigation;
17 |
--------------------------------------------------------------------------------
/readme.md:
--------------------------------------------------------------------------------
1 | # React Router Workshop
2 | A collection of mini projects showing the core features of React Router.
3 | You can run each example by navigating to the folder and typing
4 |
5 | ```
6 | npm install
7 | npm start
8 | ```
9 |
10 | All the examples use create-react-app as their base.
11 |
12 | ## The Goal
13 | To teach other (and myself) the inner working of React Router.
14 |
15 | ## Coming Soon
16 | I am going to update the mono repo to use Lerna so I can handle all the dependencies correctly.
17 |
18 | ## Help
19 | In you're interested in taking part, then send a PR or message me.
20 |
21 | .
22 |
--------------------------------------------------------------------------------