├── .gitignore
├── demo1
├── .gitignore
├── src
│ ├── index.html
│ ├── Index.jsx
│ ├── test.js
│ └── HelloMessage.jsx
├── webpack
│ ├── webpack.dev.config.js
│ ├── webpack.prod.config.js
│ └── webpack.config.js
├── server.js
├── package.json
├── assets
│ ├── index.js
│ └── index.html
└── 1.入门基础(demo1解释).md
├── demo2
├── .gitignore
├── src
│ ├── index.html
│ ├── css
│ │ └── index.css
│ ├── Index.jsx
│ ├── CenterConter.jsx
│ ├── HelloMessage.jsx
│ ├── Top.jsx
│ ├── Tree.jsx
│ └── CenterTable.jsx
├── webpack
│ ├── webpack.dev.config.js
│ ├── webpack.prod.config.js
│ └── webpack.config.js
├── 2.入门基础(demo2解释).md
├── mock
│ ├── countrylist
│ │ ├── viewstate.js
│ │ └── records.js
│ └── mainframe
│ │ └── viewstate.js
├── server.js
├── package.json
└── assets
│ ├── index.js
│ └── index.html
├── 开发测试文档.md
├── demo3
├── public
│ ├── favicon.ico
│ ├── manifest.json
│ └── index.html
├── src
│ ├── index.css
│ ├── App.test.js
│ ├── index.js
│ ├── App.js
│ ├── App.css
│ ├── logo.svg
│ ├── MyCalendar.jsx
│ └── registerServiceWorker.js
├── .idea
│ ├── encodings.xml
│ ├── misc.xml
│ ├── modules.xml
│ ├── demo3.iml
│ └── workspace.xml
├── .gitignore
├── package.json
└── README.md
├── LICENSE
└── README.md
/.gitignore:
--------------------------------------------------------------------------------
1 | /node_modules/
2 | /.idea/
--------------------------------------------------------------------------------
/demo1/.gitignore:
--------------------------------------------------------------------------------
1 | /node_modules/
2 | /.idea/
--------------------------------------------------------------------------------
/demo2/.gitignore:
--------------------------------------------------------------------------------
1 | /node_modules/
2 | /.idea/
--------------------------------------------------------------------------------
/开发测试文档.md:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lzmhost/ReactDemo/HEAD/开发测试文档.md
--------------------------------------------------------------------------------
/demo3/public/favicon.ico:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/lzmhost/ReactDemo/HEAD/demo3/public/favicon.ico
--------------------------------------------------------------------------------
/demo3/src/index.css:
--------------------------------------------------------------------------------
1 | body {
2 | margin: 0;
3 | padding: 0;
4 | font-family: sans-serif;
5 | }
6 |
--------------------------------------------------------------------------------
/demo3/.idea/encodings.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
--------------------------------------------------------------------------------
/demo1/src/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Title
6 |
7 |
8 |
9 |
10 |
--------------------------------------------------------------------------------
/demo3/.idea/misc.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
--------------------------------------------------------------------------------
/demo2/src/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 | Title
6 |
7 |
8 |
9 |
10 |
11 |
--------------------------------------------------------------------------------
/demo1/src/Index.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 | import ReactDOM from 'react-dom';
3 | import HelloMessage from './HelloMessage';
4 |
5 | ReactDOM.render(
6 |
7 | , document.getElementById('root'))
--------------------------------------------------------------------------------
/demo1/src/test.js:
--------------------------------------------------------------------------------
1 | let a1 = 1, b1 = 2, c1 = 3;
2 |
3 | export const a = function() {
4 | alert(a1);
5 | }
6 |
7 | export const b = function() {
8 | alert(b1);
9 | }
10 |
11 | export const c = function() {
12 | alert(c1);
13 | }
--------------------------------------------------------------------------------
/demo1/webpack/webpack.dev.config.js:
--------------------------------------------------------------------------------
1 | const config = require('./webpack.config.js');
2 | const path = require('path');
3 |
4 | // 开发环境使用本项目中的build目录最为编译目录。
5 | config.output.path = path.resolve(__dirname, '../assets');
6 |
7 | module.exports = config;
--------------------------------------------------------------------------------
/demo2/webpack/webpack.dev.config.js:
--------------------------------------------------------------------------------
1 | const config = require('./webpack.config.js');
2 | const path = require('path');
3 |
4 | // 开发环境使用本项目中的build目录最为编译目录。
5 | config.output.path = path.resolve(__dirname, '../assets');
6 |
7 | module.exports = config;
--------------------------------------------------------------------------------
/demo3/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 |
--------------------------------------------------------------------------------
/demo2/2.入门基础(demo2解释).md:
--------------------------------------------------------------------------------
1 | # 1.基础入门(demo2解释)
2 |
3 | ## 前言
4 | 该文档主要讲解demo2的相关结构内容,ant design是什么,怎么用。
5 | ***
6 | ## 目录
7 | 1. 简单介绍ant design;
8 | 2. 简单介绍面向对象编程
9 | 3. React项目demo2的结构;
10 | 4. fetch
11 | 5. 异步加载
12 | 6.
13 | ***
14 | ### 1.简单介绍ant design
15 |
--------------------------------------------------------------------------------
/demo3/src/index.js:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import ReactDOM from 'react-dom';
3 | import './index.css';
4 | import App from './App';
5 | import registerServiceWorker from './registerServiceWorker';
6 |
7 | ReactDOM.render( , document.getElementById('root'));
8 | registerServiceWorker();
9 |
--------------------------------------------------------------------------------
/demo3/.idea/modules.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/demo2/src/css/index.css:
--------------------------------------------------------------------------------
1 | .sty1{
2 | background-color: red;
3 | color: white;
4 | font-size: 40px;
5 | }
6 | .sty2{
7 | background-color: #666666;
8 | color: white;
9 | font-size: 40px;
10 | }
11 | .mgrt15{
12 | margin-right: 15px;
13 | }
14 | .colorRed{
15 | color: RED;
16 | }
--------------------------------------------------------------------------------
/demo3/.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.local
15 | .env.development.local
16 | .env.test.local
17 | .env.production.local
18 |
19 | npm-debug.log*
20 | yarn-debug.log*
21 | yarn-error.log*
22 |
--------------------------------------------------------------------------------
/demo3/public/manifest.json:
--------------------------------------------------------------------------------
1 | {
2 | "short_name": "React App",
3 | "name": "Create React App Sample",
4 | "icons": [
5 | {
6 | "src": "favicon.ico",
7 | "sizes": "64x64 32x32 24x24 16x16",
8 | "type": "image/x-icon"
9 | }
10 | ],
11 | "start_url": "./index.html",
12 | "display": "standalone",
13 | "theme_color": "#000000",
14 | "background_color": "#ffffff"
15 | }
16 |
--------------------------------------------------------------------------------
/demo3/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "demo3",
3 | "version": "0.1.0",
4 | "private": true,
5 | "dependencies": {
6 | "react": "^16.0.0",
7 | "react-dom": "^16.0.0",
8 | "react-scripts": "1.0.17"
9 | },
10 | "scripts": {
11 | "start": "react-scripts start",
12 | "build": "react-scripts build",
13 | "test": "react-scripts test --env=jsdom",
14 | "eject": "react-scripts eject"
15 | }
16 | }
--------------------------------------------------------------------------------
/demo2/mock/countrylist/viewstate.js:
--------------------------------------------------------------------------------
1 | module.exports = function() {
2 |
3 | let recordsGenerator = require('./records');
4 | let pagingResult = recordsGenerator();
5 |
6 | return {
7 | "btnCreateVisible": true,
8 | "btnRefreshVisible": true,
9 | "btnDeleteVisible": true,
10 | "total": pagingResult.total,
11 | "records": pagingResult.records
12 | }
13 |
14 | }
15 |
16 |
17 |
--------------------------------------------------------------------------------
/demo3/src/App.js:
--------------------------------------------------------------------------------
1 | import React, { Component } from 'react';
2 | import logo from './logo.svg';
3 | import './App.css';
4 | import MyCalendar from './MyCalendar'
5 |
6 |
7 | class App extends Component {
8 | render() {
9 | return (
10 |
15 | );
16 | }
17 | }
18 |
19 | export default App;
20 |
--------------------------------------------------------------------------------
/demo2/src/Index.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 | import ReactDOM from 'react-dom';
3 | import CenterConter from './CenterConter';
4 | import Top from './Top';
5 | import { Row, Col } from 'antd';
6 | import './css/index.css';
7 |
8 | {/* this is React 注释*/}
9 |
10 | ReactDOM.render(
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 | /* */
21 | , document.getElementById('root'))
--------------------------------------------------------------------------------
/demo1/webpack/webpack.prod.config.js:
--------------------------------------------------------------------------------
1 | const config = require('./webpack.config.js');
2 | const path = require('path');
3 |
4 | // 生产环境要将代码编译至java项目。
5 | config.output.path = path.join('C:', 'workbench', 'temp', 'react');
6 |
7 | // 资源压缩。
8 | config.plugins.push(new webpack.optimize.UglifyJsPlugin({
9 | compress: {
10 | warnings: false
11 | }
12 | }));
13 |
14 | // 去除React属性检查代码。
15 | config.module.loaders[0].query.plugins.push("transform-react-remove-prop-types");
16 |
17 | module.exports = config;
--------------------------------------------------------------------------------
/demo2/webpack/webpack.prod.config.js:
--------------------------------------------------------------------------------
1 | const config = require('./webpack.config.js');
2 | const path = require('path');
3 |
4 | // 生产环境要将代码编译至java项目。
5 | config.output.path = path.join('C:', 'workbench', 'temp', 'react');
6 |
7 | // 资源压缩。
8 | config.plugins.push(new webpack.optimize.UglifyJsPlugin({
9 | compress: {
10 | warnings: false
11 | }
12 | }));
13 |
14 | // 去除React属性检查代码。
15 | config.module.loaders[0].query.plugins.push("transform-react-remove-prop-types");
16 |
17 | module.exports = config;
--------------------------------------------------------------------------------
/demo3/.idea/demo3.iml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
--------------------------------------------------------------------------------
/demo3/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-title {
18 | font-size: 1.5em;
19 | }
20 |
21 | .App-intro {
22 | font-size: large;
23 | }
24 |
25 | @keyframes App-logo-spin {
26 | from { transform: rotate(0deg); }
27 | to { transform: rotate(360deg); }
28 | }
29 |
--------------------------------------------------------------------------------
/demo2/mock/countrylist/records.js:
--------------------------------------------------------------------------------
1 | module.exports = function() {
2 |
3 | let Mock = require('mockjs');
4 | let datas = Mock.mock({
5 | "array|15": [{
6 | "key": '@word',
7 | "no": '@word',
8 | "code": '@word',
9 | "countryname": '@county',
10 | "customer": '@cname',
11 | "workshop": '@word',
12 | "engineer": '@cname',
13 | "active|1": true,
14 | }]
15 | });
16 |
17 | return {
18 | "records": datas.array,
19 | "total": 120
20 | }
21 |
22 | }
23 |
24 |
25 |
--------------------------------------------------------------------------------
/demo1/src/HelloMessage.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import PropTypes from 'prop-types';
3 | import { a, b } from './test';
4 |
5 | class HelloMessage extends React.Component {
6 |
7 | constructor(props) {
8 | super(props);
9 |
10 | this.state = {
11 | textVisible: false
12 | }
13 | }
14 |
15 | handClick() {
16 | this.setState({
17 | textVisible: !this.state.textVisible
18 | });
19 | }
20 |
21 | handClick2() {
22 | a();
23 | }
24 |
25 | render() {
26 |
27 | let text = null;
28 | if (this.state.textVisible) {
29 | text = {this.props.text} ;
30 | }
31 |
32 | return (
33 |
34 | this.handClick2(e)}>访问引入模块的接口
35 | this.handClick(e)}>显示|隐藏
36 | {text}
37 |
38 | )
39 |
40 | }
41 |
42 | }
43 |
44 | HelloMessage.propTypes = {
45 | text: PropTypes.string.isRequired,
46 | };
47 |
48 | export default HelloMessage;
--------------------------------------------------------------------------------
/demo1/server.js:
--------------------------------------------------------------------------------
1 | const WebpackDevServer = require('webpack-dev-server');
2 | const webpack = require('webpack');
3 | const config = require('./webpack/webpack.dev.config.js');
4 | const URL = require('url');
5 | const host = 'localhost';
6 | const port = 9090;
7 |
8 | // 项目资源访问路径,打包后的js和css都是通过下面的地址引用的。
9 | config.output.publicPath = '/assets/';
10 |
11 | // 热替换脚本。这两个脚本必须和index打在一起,否则不生效。
12 | config.entry.index.unshift('webpack-dev-server/client?http://' + host + ':' + port, 'webpack/hot/dev-server'); // 指定webpack-dev-server的host+port。
13 |
14 | // 热替换插件。
15 | config.plugins.push(new webpack.HotModuleReplacementPlugin());
16 |
17 | const compiler = webpack(config);
18 | const server = new WebpackDevServer(compiler, {
19 | hot: true,
20 | host: host,
21 | port: port,
22 | inline: true,
23 | stats: {
24 | colors: true
25 | },
26 | contentBase: '/',
27 | publicPath: config.output.publicPath
28 | });
29 |
30 | server.use('/api/*', function(req, res) {
31 | let baseUrl = req.baseUrl;
32 | baseUrl = baseUrl.replace('/api/', '/mock/');
33 | let data = require('./' + baseUrl + '.json');
34 | res.json(data);
35 | });
36 |
37 | server.listen(9090);
--------------------------------------------------------------------------------
/demo2/server.js:
--------------------------------------------------------------------------------
1 | const WebpackDevServer = require('webpack-dev-server');
2 | const webpack = require('webpack');
3 | const config = require('./webpack/webpack.dev.config.js');
4 | const URL = require('url');
5 | const host = 'localhost';
6 | const port = 9090;
7 |
8 | // 项目资源访问路径,打包后的js和css都是通过下面的地址引用的。
9 | config.output.publicPath = '/assets/';
10 |
11 | // 热替换脚本。这两个脚本必须和index打在一起,否则不生效。
12 | config.entry.index.unshift('webpack-dev-server/client?http://' + host + ':' + port, 'webpack/hot/dev-server'); // 指定webpack-dev-server的host+port。
13 |
14 | // 热替换插件。
15 | config.plugins.push(new webpack.HotModuleReplacementPlugin());
16 |
17 | const compiler = webpack(config);
18 | const server = new WebpackDevServer(compiler, {
19 | hot: true,
20 | host: host,
21 | port: port,
22 | inline: true,
23 | stats: {
24 | colors: true
25 | },
26 | contentBase: '/',
27 | publicPath: config.output.publicPath
28 | });
29 |
30 | server.use('/api/*', function(req, res) {
31 | let baseUrl = req.baseUrl;
32 | baseUrl = baseUrl.replace('/api/', '/mock/');
33 | let data = require('./' + baseUrl + '.js');
34 | let dataJson = data();
35 | res.json(dataJson);
36 | });
37 |
38 | server.listen(9090);
--------------------------------------------------------------------------------
/demo2/src/CenterConter.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 | import CenterTable from './CenterTable';
3 | import Tree1 from './Tree';
4 | import { Row, Col } from 'antd';
5 | var newState1
6 | class CenterConter extends React.Component {
7 | constructor(props) {
8 | super(props);
9 | this.state= {
10 | a : []
11 | }
12 | }
13 |
14 | onChildChanged(newState) {
15 | // console.log(newState)
16 | newState.map(function(item){
17 | item.name = item.text
18 | item.age = 1
19 | item.address = item.text
20 | })
21 | this.setState({
22 | a: newState,
23 | })
24 | return newState;
25 | }
26 | render(){
27 | return(
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 | )
38 | }
39 | }
40 |
41 | export default CenterConter
--------------------------------------------------------------------------------
/demo2/src/HelloMessage.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react';
2 | import PropTypes from 'prop-types';
3 | import { a, b } from './Tree';
4 |
5 |
6 | class HelloMessage extends React.Component {
7 |
8 | constructor(props) {
9 | super(props);
10 |
11 | this.state = {
12 | textVisible: false
13 | }
14 | }
15 |
16 | handClick() {
17 | this.setState({
18 | textVisible: !this.state.textVisible
19 | });
20 | }
21 | onSelect(selectedKeys, info){
22 | return (
23 | console.log('selected', selectedKeys, info)
24 | )
25 | }
26 | handClick2() {
27 | a();
28 | }
29 |
30 | render() {
31 |
32 | let text = null;
33 | if (this.state.textVisible) {
34 | text = {this.props.text} ;
35 | }
36 |
37 | return (
38 |
39 |
40 | this.handClick2(e)}>访问引入模块的接口
41 | this.handClick(e)}>显示|隐藏
42 | {text}
43 |
44 | )
45 |
46 | }
47 |
48 | }
49 |
50 | HelloMessage.propTypes = {
51 | text: PropTypes.string.isRequired,
52 | };
53 |
54 | export default HelloMessage;
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Copyright (c) 2017, 李啸吟
2 | All rights reserved.
3 |
4 | Redistribution and use in source and binary forms, with or without modification,
5 | are permitted provided that the following conditions are met:
6 |
7 | * Redistributions of source code must retain the above copyright notice, this
8 | list of conditions and the following disclaimer.
9 |
10 | * Redistributions in binary form must reproduce the above copyright notice, this
11 | list of conditions and the following disclaimer in the documentation and/or
12 | other materials provided with the distribution.
13 |
14 | * Neither the name of the {organization} nor the names of its
15 | contributors may be used to endorse or promote products derived from
16 | this software without specific prior written permission.
17 |
18 | THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
19 | ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
20 | WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
21 | DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
22 | ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
23 | (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
24 | LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
25 | ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
26 | (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
27 | SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
--------------------------------------------------------------------------------
/demo1/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "demo1",
3 | "version": "1.0.0",
4 | "description": "",
5 | "main": "index.js",
6 | "scripts": {
7 | "test": "echo \"Error: no test specified\" && exit 1",
8 | "build-dev": "webpack --config webpack/webpack.dev.config.js",
9 | "build": "webpack --config webpack/webpack.prod.config.js",
10 | "start": "node server.js"
11 | },
12 | "author": "",
13 | "license": "ISC",
14 | "devDependencies": {
15 | "babel-core": "^6.26.0",
16 | "babel-loader": "^7.1.2",
17 | "babel-plugin-import": "^1.4.0",
18 | "babel-plugin-transform-react-remove-prop-types": "^0.4.8",
19 | "babel-preset-env": "^1.6.0",
20 | "babel-preset-es2015": "^6.24.1",
21 | "babel-preset-react": "^6.24.1",
22 | "css-loader": "^0.28.5",
23 | "extract-text-webpack-plugin": "^3.0.0",
24 | "file-loader": "^0.11.2",
25 | "html-webpack-plugin": "^2.30.1",
26 | "install": "^0.10.1",
27 | "mockjs": "^1.0.1-beta3",
28 | "postcss-loader": "^2.0.6",
29 | "react-router-dom": "^4.2.0",
30 | "style-loader": "^0.18.2",
31 | "url-loader": "^0.5.9",
32 | "webpack": "^3.5.5",
33 | "webpack-dev-server": "^2.7.1",
34 | "webpack-link": "^0.2.0"
35 | },
36 | "dependencies": {
37 | "antd": "^2.12.7",
38 | "babel-polyfill": "^6.26.0",
39 | "es6-promise": "^4.1.1",
40 | "isomorphic-fetch": "^2.2.1",
41 | "prop-types": "^15.5.10",
42 | "react": "^15.6.1",
43 | "react-dom": "^15.6.1",
44 | "react-redux": "^5.0.6",
45 | "react-router": "^4.1.2",
46 | "redux": "^3.7.2",
47 | "redux-thunk": "^2.2.0",
48 | "commons-react": "git+https://git.oschina.net/magicsoft/commons-react.git"
49 | }
50 | }
51 |
--------------------------------------------------------------------------------
/demo2/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "demo2",
3 | "version": "1.0.0",
4 | "description": "",
5 | "main": "index.js",
6 | "scripts": {
7 | "test": "echo \"Error: no test specified\" && exit 1",
8 | "build-dev": "webpack --config webpack/webpack.dev.config.js",
9 | "build": "webpack --config webpack/webpack.prod.config.js",
10 | "start": "node server.js"
11 | },
12 | "author": "",
13 | "license": "ISC",
14 | "devDependencies": {
15 | "babel-core": "^6.26.0",
16 | "babel-loader": "^7.1.2",
17 | "babel-plugin-import": "^1.4.0",
18 | "babel-plugin-transform-react-remove-prop-types": "^0.4.8",
19 | "babel-preset-env": "^1.6.0",
20 | "babel-preset-es2015": "^6.24.1",
21 | "babel-preset-react": "^6.24.1",
22 | "css-loader": "^0.28.5",
23 | "extract-text-webpack-plugin": "^3.0.0",
24 | "file-loader": "^0.11.2",
25 | "html-webpack-plugin": "^2.30.1",
26 | "install": "^0.10.1",
27 | "mockjs": "^1.0.1-beta3",
28 | "postcss-loader": "^2.0.6",
29 | "react-router-dom": "^4.2.0",
30 | "style-loader": "^0.18.2",
31 | "url-loader": "^0.5.9",
32 | "webpack": "^3.5.5",
33 | "webpack-dev-server": "^2.7.1",
34 | "webpack-link": "^0.2.0"
35 | },
36 | "dependencies": {
37 | "antd": "^2.12.7",
38 | "babel-polyfill": "^6.26.0",
39 | "commons-react": "git+https://git.oschina.net/magicsoft/commons-react.git",
40 | "es6-promise": "^4.1.1",
41 | "fetch": "^1.1.0",
42 | "isomorphic-fetch": "^2.2.1",
43 | "prop-types": "^15.5.10",
44 | "react": "^15.6.1",
45 | "react-dom": "^15.6.1",
46 | "react-redux": "^5.0.6",
47 | "react-router": "^4.1.2",
48 | "redux": "^3.7.2",
49 | "redux-thunk": "^2.2.0"
50 | }
51 | }
52 |
--------------------------------------------------------------------------------
/demo3/public/index.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
11 |
12 |
13 |
22 | React App
23 |
24 |
25 |
26 | You need to enable JavaScript to run this app.
27 |
28 |
29 |
39 |
40 |
41 |
--------------------------------------------------------------------------------
/demo2/src/Top.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 | import { Row, Col, Select,Checkbox } from 'antd';
3 | const Option = Select.Option;
4 |
5 | function handleChange(e){
6 | console.log('click ', e);
7 | }
8 | function onChange(e) {
9 | console.log(`checked = ${e.target.checked}`);
10 | }
11 | class Top extends React.Component{
12 | constructor(props) {
13 | super(props);
14 | this.state = {
15 |
16 | }
17 | }
18 |
19 |
20 | render() {
21 | return (
22 |
23 |
24 |
25 | 干部库:
26 |
27 | 在职
28 | 离职
29 | 挂职
30 | 其他
31 |
32 |
33 |
34 | 所属单位:
35 |
36 | 人事关系所在单位
37 | 公司职位所在单位
38 | 行政职务所在单位
39 |
40 |
41 |
42 |
43 | 显示所有下级
44 |
45 |
46 |
47 |
48 | );
49 | }
50 | }
51 |
52 | export default Top;
53 |
--------------------------------------------------------------------------------
/demo2/mock/mainframe/viewstate.js:
--------------------------------------------------------------------------------
1 | module.exports = function() {
2 | return {
3 | "userName": "Test User",
4 | "selectedMenus": ["1"],
5 | "openMenus": ["5", "13", "18"],
6 | "menuItems": [{
7 | "text": "Home", "key": "1", "url": "/"
8 | }, {
9 | "text": "Work Order", "key": "2"
10 | }, {
11 | "text": "Winder", "key": "3"
12 | }, {
13 | "text": "Solutions", "key": "4"
14 | }, {
15 | "text": "Statistic & Report", "key": "5",
16 | "items": [{
17 | "text": "Monthly Report", "key": "6"
18 | }, {
19 | "text": "Successful Rate", "key": "7"
20 | }, {
21 | "text": "Malfunction Type", "key": "8"
22 | }, {
23 | "text": "Component Failure", "key": "9"
24 | }, {
25 | "text": "Life Analysis for OTA & Local Spare Part", "key": "10"
26 | }, {
27 | "text": "Life Analysis for OTA & Local Spare Part", "key": "11"
28 | }, {
29 | "text": "Life Analysis for Repair Spare part", "key": "12"
30 | }]
31 | }, {
32 | "text": "Master Data", "key": "13",
33 | "items": [{
34 | "text": "Basic Definition", "key": "14"
35 | }, {
36 | "text": "Parts", "key": "15"
37 | }, {
38 | "text": "Maintenance Plan", "key": "16"
39 | }, {
40 | "text": "Project Order", "key": "17"
41 | }]
42 | }, {
43 | "text": "System Admin", "key": "18",
44 | "items": [{
45 | "text": "Countries", "key": "19", "url": "/countrylist"
46 | }, {
47 | "text": "Customers", "key": "20"
48 | }, {
49 | "text": "Workshop", "key": "21"
50 | }, {
51 | "text": "Users", "key": "22"
52 | }, {
53 | "text": "Role", "key": "23"
54 | }, {
55 | "text": "Assign Rights", "key": "24"
56 | }]
57 | }]
58 | }
59 |
60 | }
--------------------------------------------------------------------------------
/demo3/src/logo.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
--------------------------------------------------------------------------------
/demo1/assets/index.js:
--------------------------------------------------------------------------------
1 | /******/ (function(modules) { // webpackBootstrap
2 | /******/ // The module cache
3 | /******/ var installedModules = {};
4 | /******/
5 | /******/ // The require function
6 | /******/ function __webpack_require__(moduleId) {
7 | /******/
8 | /******/ // Check if module is in cache
9 | /******/ if(installedModules[moduleId]) {
10 | /******/ return installedModules[moduleId].exports;
11 | /******/ }
12 | /******/ // Create a new module (and put it into the cache)
13 | /******/ var module = installedModules[moduleId] = {
14 | /******/ i: moduleId,
15 | /******/ l: false,
16 | /******/ exports: {}
17 | /******/ };
18 | /******/
19 | /******/ // Execute the module function
20 | /******/ modules[moduleId].call(module.exports, module, module.exports, __webpack_require__);
21 | /******/
22 | /******/ // Flag the module as loaded
23 | /******/ module.l = true;
24 | /******/
25 | /******/ // Return the exports of the module
26 | /******/ return module.exports;
27 | /******/ }
28 | /******/
29 | /******/
30 | /******/ // expose the modules object (__webpack_modules__)
31 | /******/ __webpack_require__.m = modules;
32 | /******/
33 | /******/ // expose the module cache
34 | /******/ __webpack_require__.c = installedModules;
35 | /******/
36 | /******/ // define getter function for harmony exports
37 | /******/ __webpack_require__.d = function(exports, name, getter) {
38 | /******/ if(!__webpack_require__.o(exports, name)) {
39 | /******/ Object.defineProperty(exports, name, {
40 | /******/ configurable: false,
41 | /******/ enumerable: true,
42 | /******/ get: getter
43 | /******/ });
44 | /******/ }
45 | /******/ };
46 | /******/
47 | /******/ // getDefaultExport function for compatibility with non-harmony modules
48 | /******/ __webpack_require__.n = function(module) {
49 | /******/ var getter = module && module.__esModule ?
50 | /******/ function getDefault() { return module['default']; } :
51 | /******/ function getModuleExports() { return module; };
52 | /******/ __webpack_require__.d(getter, 'a', getter);
53 | /******/ return getter;
54 | /******/ };
55 | /******/
56 | /******/ // Object.prototype.hasOwnProperty.call
57 | /******/ __webpack_require__.o = function(object, property) { return Object.prototype.hasOwnProperty.call(object, property); };
58 | /******/
59 | /******/ // __webpack_public_path__
60 | /******/ __webpack_require__.p = "";
61 | /******/
62 | /******/ // Load entry module and return exports
63 | /******/ return __webpack_require__(__webpack_require__.s = 0);
64 | /******/ })
65 | /************************************************************************/
66 | /******/ ([
67 | /* 0 */
68 | /***/ (function(module, exports, __webpack_require__) {
69 |
70 | module.exports = __webpack_require__(1);
71 |
72 |
73 | /***/ }),
74 | /* 1 */
75 | /***/ (function(module, exports) {
76 |
77 | throw new Error("Module parse failed: G:\\magicsoft\\git-repository\\commons-react-demo\\demo1\\Index.jsx Unexpected token (6:12)\nYou may need an appropriate loader to handle this file type.\n| render(){\r\n| return (\r\n| \r\n| {this.props.children}\r\n|
\r");
78 |
79 | /***/ })
80 | /******/ ]);
--------------------------------------------------------------------------------
/demo2/assets/index.js:
--------------------------------------------------------------------------------
1 | /******/ (function(modules) { // webpackBootstrap
2 | /******/ // The module cache
3 | /******/ var installedModules = {};
4 | /******/
5 | /******/ // The require function
6 | /******/ function __webpack_require__(moduleId) {
7 | /******/
8 | /******/ // Check if module is in cache
9 | /******/ if(installedModules[moduleId]) {
10 | /******/ return installedModules[moduleId].exports;
11 | /******/ }
12 | /******/ // Create a new module (and put it into the cache)
13 | /******/ var module = installedModules[moduleId] = {
14 | /******/ i: moduleId,
15 | /******/ l: false,
16 | /******/ exports: {}
17 | /******/ };
18 | /******/
19 | /******/ // Execute the module function
20 | /******/ modules[moduleId].call(module.exports, module, module.exports, __webpack_require__);
21 | /******/
22 | /******/ // Flag the module as loaded
23 | /******/ module.l = true;
24 | /******/
25 | /******/ // Return the exports of the module
26 | /******/ return module.exports;
27 | /******/ }
28 | /******/
29 | /******/
30 | /******/ // expose the modules object (__webpack_modules__)
31 | /******/ __webpack_require__.m = modules;
32 | /******/
33 | /******/ // expose the module cache
34 | /******/ __webpack_require__.c = installedModules;
35 | /******/
36 | /******/ // define getter function for harmony exports
37 | /******/ __webpack_require__.d = function(exports, name, getter) {
38 | /******/ if(!__webpack_require__.o(exports, name)) {
39 | /******/ Object.defineProperty(exports, name, {
40 | /******/ configurable: false,
41 | /******/ enumerable: true,
42 | /******/ get: getter
43 | /******/ });
44 | /******/ }
45 | /******/ };
46 | /******/
47 | /******/ // getDefaultExport function for compatibility with non-harmony modules
48 | /******/ __webpack_require__.n = function(module) {
49 | /******/ var getter = module && module.__esModule ?
50 | /******/ function getDefault() { return module['default']; } :
51 | /******/ function getModuleExports() { return module; };
52 | /******/ __webpack_require__.d(getter, 'a', getter);
53 | /******/ return getter;
54 | /******/ };
55 | /******/
56 | /******/ // Object.prototype.hasOwnProperty.call
57 | /******/ __webpack_require__.o = function(object, property) { return Object.prototype.hasOwnProperty.call(object, property); };
58 | /******/
59 | /******/ // __webpack_public_path__
60 | /******/ __webpack_require__.p = "";
61 | /******/
62 | /******/ // Load entry module and return exports
63 | /******/ return __webpack_require__(__webpack_require__.s = 0);
64 | /******/ })
65 | /************************************************************************/
66 | /******/ ([
67 | /* 0 */
68 | /***/ (function(module, exports, __webpack_require__) {
69 |
70 | module.exports = __webpack_require__(1);
71 |
72 |
73 | /***/ }),
74 | /* 1 */
75 | /***/ (function(module, exports) {
76 |
77 | throw new Error("Module parse failed: G:\\magicsoft\\git-repository\\commons-react-demo\\demo1\\Index.jsx Unexpected token (6:12)\nYou may need an appropriate loader to handle this file type.\n| render(){\r\n| return (\r\n| \r\n| {this.props.children}\r\n|
\r");
78 |
79 | /***/ })
80 | /******/ ]);
--------------------------------------------------------------------------------
/demo3/src/MyCalendar.jsx:
--------------------------------------------------------------------------------
1 | import React, { Component } from 'react';
2 |
3 | let mytrsArr =[];
4 | class MyCalendar extends Component {
5 | constructor(props) {
6 | super(props);
7 | this.state = this.getInitialState();
8 | this.getTrs()
9 | }
10 | getInitialState() {
11 | return {
12 | startNumber: 0,
13 | addNumber : 30,
14 | endNumber : 0+60*12,
15 | events : [
16 | {start:30,end:150},
17 | {start:540,end:600},
18 | {start:560,end:620},
19 | {start:610,end:670},
20 | ]
21 | }
22 | }
23 | getEvents(){
24 | let events = [
25 | {start:30,end:150},
26 | {start:540,end:600},
27 | {start:560,end:620},
28 | {start:610,end:670},
29 | ]
30 | for(let item = 0;item
50 |
51 | {this.state.events.map((item)=>{
52 | return(
53 |
54 |
Sample Item
55 |
`````````
56 |
57 | )
58 | })}
59 | {mytrsArr.map((u) => {
60 | if(u.time%60==0){
61 | return (
62 | {9 + parseInt(u.time/60)+":00"}
63 |
64 | );
65 | }else if(u.time%30==0){
66 | return (
67 | {9 + parseInt(u.time/60)+":"+u.time%60}
68 |
69 | );
70 | }
71 |
72 | })}
73 |
74 |
75 | );
76 | }
77 | }
78 |
79 | export default MyCalendar;
--------------------------------------------------------------------------------
/demo1/assets/index.html:
--------------------------------------------------------------------------------
1 | Html Webpack Plugin:
2 |
3 | Error: Child compilation failed:
4 | Entry module not found: Error: Can't resolve 'G:\magicsoft\git-repository\commons-react-demo\demo1\src\index.html' in 'G:\magicsoft\git-repository\commons-react-demo\demo1':
5 | Error: Can't resolve 'G:\magicsoft\git-repository\commons-react-demo\demo1\src\index.html' in 'G:\magicsoft\git-repository\commons-react-demo\demo1'
6 |
7 | - compiler.js:76
8 | [demo1]/[html-webpack-plugin]/lib/compiler.js:76:16
9 |
10 | - Compiler.js:304 compile
11 | [demo1]/[webpack]/lib/Compiler.js:304:11
12 |
13 | - Compiler.js:520 applyPluginsAsync.err
14 | [demo1]/[webpack]/lib/Compiler.js:520:14
15 |
16 | - Tapable.js:202 next
17 | [demo1]/[tapable]/lib/Tapable.js:202:11
18 |
19 | - CachePlugin.js:62 Compiler.
20 | [demo1]/[webpack]/lib/CachePlugin.js:62:5
21 |
22 | - Tapable.js:206 Compiler.applyPluginsAsyncSeries
23 | [demo1]/[tapable]/lib/Tapable.js:206:13
24 |
25 | - Compiler.js:517 compilation.seal.err
26 | [demo1]/[webpack]/lib/Compiler.js:517:11
27 |
28 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
29 | [demo1]/[tapable]/lib/Tapable.js:195:46
30 |
31 | - Compilation.js:671 self.applyPluginsAsync.err
32 | [demo1]/[webpack]/lib/Compilation.js:671:19
33 |
34 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
35 | [demo1]/[tapable]/lib/Tapable.js:195:46
36 |
37 | - Compilation.js:662 self.applyPluginsAsync.err
38 | [demo1]/[webpack]/lib/Compilation.js:662:11
39 |
40 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
41 | [demo1]/[tapable]/lib/Tapable.js:195:46
42 |
43 | - Compilation.js:657 self.applyPluginsAsync.err
44 | [demo1]/[webpack]/lib/Compilation.js:657:10
45 |
46 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
47 | [demo1]/[tapable]/lib/Tapable.js:195:46
48 |
49 | - Compilation.js:653 sealPart2
50 | [demo1]/[webpack]/lib/Compilation.js:653:9
51 |
52 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
53 | [demo1]/[tapable]/lib/Tapable.js:195:46
54 |
55 | - Compilation.js:596 Compilation.seal
56 | [demo1]/[webpack]/lib/Compilation.js:596:8
57 |
58 | - Compiler.js:514 applyPluginsParallel.err
59 | [demo1]/[webpack]/lib/Compiler.js:514:17
60 |
61 | - Tapable.js:289
62 | [demo1]/[tapable]/lib/Tapable.js:289:11
63 |
64 | - Compilation.js:498 _addModuleChain
65 | [demo1]/[webpack]/lib/Compilation.js:498:11
66 |
67 | - Compilation.js:381 errorAndCallback.bail
68 | [demo1]/[webpack]/lib/Compilation.js:381:4
69 |
70 | - Compilation.js:404 moduleFactory.create
71 | [demo1]/[webpack]/lib/Compilation.js:404:13
72 |
73 | - NormalModuleFactory.js:235 factory
74 | [demo1]/[webpack]/lib/NormalModuleFactory.js:235:20
75 |
76 | - NormalModuleFactory.js:60 resolver
77 | [demo1]/[webpack]/lib/NormalModuleFactory.js:60:20
78 |
79 | - NormalModuleFactory.js:127 asyncLib.parallel.e
80 | [demo1]/[webpack]/lib/NormalModuleFactory.js:127:20
81 |
82 | - async.js:3861
83 | [demo1]/[async]/dist/async.js:3861:9
84 |
85 | - async.js:421
86 | [demo1]/[async]/dist/async.js:421:16
87 |
88 | - async.js:996 iteratorCallback
89 | [demo1]/[async]/dist/async.js:996:13
90 |
91 | - async.js:906
92 | [demo1]/[async]/dist/async.js:906:16
93 |
94 | - async.js:3858
95 | [demo1]/[async]/dist/async.js:3858:13
96 |
97 |
--------------------------------------------------------------------------------
/demo2/assets/index.html:
--------------------------------------------------------------------------------
1 | Html Webpack Plugin:
2 |
3 | Error: Child compilation failed:
4 | Entry module not found: Error: Can't resolve 'G:\magicsoft\git-repository\commons-react-demo\demo1\src\index.html' in 'G:\magicsoft\git-repository\commons-react-demo\demo1':
5 | Error: Can't resolve 'G:\magicsoft\git-repository\commons-react-demo\demo1\src\index.html' in 'G:\magicsoft\git-repository\commons-react-demo\demo1'
6 |
7 | - compiler.js:76
8 | [demo1]/[html-webpack-plugin]/lib/compiler.js:76:16
9 |
10 | - Compiler.js:304 compile
11 | [demo1]/[webpack]/lib/Compiler.js:304:11
12 |
13 | - Compiler.js:520 applyPluginsAsync.err
14 | [demo1]/[webpack]/lib/Compiler.js:520:14
15 |
16 | - Tapable.js:202 next
17 | [demo1]/[tapable]/lib/Tapable.js:202:11
18 |
19 | - CachePlugin.js:62 Compiler.
20 | [demo1]/[webpack]/lib/CachePlugin.js:62:5
21 |
22 | - Tapable.js:206 Compiler.applyPluginsAsyncSeries
23 | [demo1]/[tapable]/lib/Tapable.js:206:13
24 |
25 | - Compiler.js:517 compilation.seal.err
26 | [demo1]/[webpack]/lib/Compiler.js:517:11
27 |
28 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
29 | [demo1]/[tapable]/lib/Tapable.js:195:46
30 |
31 | - Compilation.js:671 self.applyPluginsAsync.err
32 | [demo1]/[webpack]/lib/Compilation.js:671:19
33 |
34 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
35 | [demo1]/[tapable]/lib/Tapable.js:195:46
36 |
37 | - Compilation.js:662 self.applyPluginsAsync.err
38 | [demo1]/[webpack]/lib/Compilation.js:662:11
39 |
40 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
41 | [demo1]/[tapable]/lib/Tapable.js:195:46
42 |
43 | - Compilation.js:657 self.applyPluginsAsync.err
44 | [demo1]/[webpack]/lib/Compilation.js:657:10
45 |
46 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
47 | [demo1]/[tapable]/lib/Tapable.js:195:46
48 |
49 | - Compilation.js:653 sealPart2
50 | [demo1]/[webpack]/lib/Compilation.js:653:9
51 |
52 | - Tapable.js:195 Compilation.applyPluginsAsyncSeries
53 | [demo1]/[tapable]/lib/Tapable.js:195:46
54 |
55 | - Compilation.js:596 Compilation.seal
56 | [demo1]/[webpack]/lib/Compilation.js:596:8
57 |
58 | - Compiler.js:514 applyPluginsParallel.err
59 | [demo1]/[webpack]/lib/Compiler.js:514:17
60 |
61 | - Tapable.js:289
62 | [demo1]/[tapable]/lib/Tapable.js:289:11
63 |
64 | - Compilation.js:498 _addModuleChain
65 | [demo1]/[webpack]/lib/Compilation.js:498:11
66 |
67 | - Compilation.js:381 errorAndCallback.bail
68 | [demo1]/[webpack]/lib/Compilation.js:381:4
69 |
70 | - Compilation.js:404 moduleFactory.create
71 | [demo1]/[webpack]/lib/Compilation.js:404:13
72 |
73 | - NormalModuleFactory.js:235 factory
74 | [demo1]/[webpack]/lib/NormalModuleFactory.js:235:20
75 |
76 | - NormalModuleFactory.js:60 resolver
77 | [demo1]/[webpack]/lib/NormalModuleFactory.js:60:20
78 |
79 | - NormalModuleFactory.js:127 asyncLib.parallel.e
80 | [demo1]/[webpack]/lib/NormalModuleFactory.js:127:20
81 |
82 | - async.js:3861
83 | [demo1]/[async]/dist/async.js:3861:9
84 |
85 | - async.js:421
86 | [demo1]/[async]/dist/async.js:421:16
87 |
88 | - async.js:996 iteratorCallback
89 | [demo1]/[async]/dist/async.js:996:13
90 |
91 | - async.js:906
92 | [demo1]/[async]/dist/async.js:906:16
93 |
94 | - async.js:3858
95 | [demo1]/[async]/dist/async.js:3858:13
96 |
97 |
--------------------------------------------------------------------------------
/demo1/webpack/webpack.config.js:
--------------------------------------------------------------------------------
1 | const path = require('path');
2 | const HtmlWebpackPlugin = require('html-webpack-plugin');
3 | const CommonsChunkPlugin = require("webpack/lib/optimize/CommonsChunkPlugin");
4 |
5 | // css打包插件。
6 | const ExtractTextPlugin = require('extract-text-webpack-plugin');
7 | const extractTextPlugin = new ExtractTextPlugin('index.css', {
8 | disable: false,
9 | allChunks: true
10 | });
11 |
12 | module.exports = {
13 | entry: {// 打包(计算依赖)的入口文件。
14 | 'index': [path.resolve(__dirname, '../src/Index.jsx')],
15 | // 'react': ['react', 'react-dom', 'react-redux', 'react-router-dom', 'redux', 'redux-thunk', 'react-router', 'babel-polyfill', 'isomorphic-fetch'],
16 | // 'antd': ['antd']
17 | },
18 | output: {
19 | filename: '[name].js' // 编译结果的输出文件,[name]指的是来源entry中的文件名。
20 | },
21 | resolve: {
22 | extensions: ['.js', '.jsx'],
23 | alias: {
24 | 'react': path.resolve(__dirname, '../node_modules/react'),
25 | 'react-dom': path.resolve(__dirname, '../node_modules/react-dom'),
26 | 'react-redux': path.resolve(__dirname, '../node_modules/react-redux'),
27 | 'react-router-dom': path.resolve(__dirname, '../node_modules/react-router-dom'),
28 | 'redux': path.resolve(__dirname, '../node_modules/redux'),
29 | 'redux-thunk': path.resolve(__dirname, '../node_modules/redux-thunk'),
30 | 'react-router': path.resolve(__dirname, '../node_modules/react-router'),
31 | 'babel-polyfill': path.resolve(__dirname, '../node_modules/babel-polyfill'),
32 | 'isomorphic-fetch': path.resolve(__dirname, '../node_modules/isomorphic-fetch'),
33 | 'antd': path.resolve(__dirname, '../node_modules/antd'),
34 | }
35 | },
36 | module: {
37 | loaders: [
38 | {
39 | // 打包React代码需要引用Babel作为翻译器,并加入es2015, react等特性。
40 | test: /\.(js|jsx)$/,
41 | include: [path.resolve(__dirname, '../src')], //C:\workbench\git-repository\org.magicsoft\commons-react\ //path.resolve(__dirname, '../node_modules/commons-react'),
42 | loader: require.resolve('babel-loader'),
43 | query: {
44 | presets: ['es2015', 'react'],
45 | plugins: [
46 | ['import', { libraryName: 'antd', style: 'css' }] // `style: true` 会加载 less 文件
47 | ]
48 | }
49 | },
50 | {
51 | test: /\.css$/,
52 | loader: extractTextPlugin.extract('css-loader') // css打包。
53 | },
54 | {
55 | test: /\.(png|jpg|gif|svg)$/,
56 | loader: require.resolve('url-loader'),
57 | query: {
58 | limit: 10000, // 小于这个字节的图片会被打包成base64字符串。
59 | name: 'images/[name].[ext]?[hash:7]'
60 | }
61 | }
62 | ]
63 | },
64 | plugins: [
65 | extractTextPlugin, // 此插件的目的是将css单独打包成一个文件(不加的话css是会被打到js中的。)
66 | new HtmlWebpackPlugin({ //根据模板插入css/js等生成最终HTML
67 | filename: 'index.html', //生成的html存放路径,相对于 path
68 | template: 'src/index.html', // Load a custom template
69 | inject: true, //允许插件修改哪些内容,包括head与body
70 | hash: true, //为静态资源生成hash值
71 | // chunks: ['webpack-dev-server', 'index'] // 如果不指定这项,会把所有脚本都加载进来,指定了就只加载指定的脚本。
72 | }),
73 | // new CommonsChunkPlugin({
74 | // names: ['antd','react']
75 | // })
76 | ]
77 | }
--------------------------------------------------------------------------------
/demo2/webpack/webpack.config.js:
--------------------------------------------------------------------------------
1 | const path = require('path');
2 | const HtmlWebpackPlugin = require('html-webpack-plugin');
3 | const CommonsChunkPlugin = require("webpack/lib/optimize/CommonsChunkPlugin");
4 |
5 | // css打包插件。
6 | const ExtractTextPlugin = require('extract-text-webpack-plugin');
7 | const extractTextPlugin = new ExtractTextPlugin('index.css', {
8 | disable: false,
9 | allChunks: true
10 | });
11 |
12 | module.exports = {
13 | entry: {// 打包(计算依赖)的入口文件。
14 | 'index': [path.resolve(__dirname, '../src/Index.jsx')],
15 | // 'react': ['react', 'react-dom', 'react-redux', 'react-router-dom', 'redux', 'redux-thunk', 'react-router', 'babel-polyfill', 'isomorphic-fetch'],
16 | // 'antd': ['antd']
17 | },
18 | output: {
19 | filename: '[name].js' // 编译结果的输出文件,[name]指的是来源entry中的文件名。
20 | },
21 | resolve: {
22 | extensions: ['.js', '.jsx'],
23 | alias: {
24 | 'react': path.resolve(__dirname, '../node_modules/react'),
25 | 'react-dom': path.resolve(__dirname, '../node_modules/react-dom'),
26 | 'react-redux': path.resolve(__dirname, '../node_modules/react-redux'),
27 | 'react-router-dom': path.resolve(__dirname, '../node_modules/react-router-dom'),
28 | 'redux': path.resolve(__dirname, '../node_modules/redux'),
29 | 'redux-thunk': path.resolve(__dirname, '../node_modules/redux-thunk'),
30 | 'react-router': path.resolve(__dirname, '../node_modules/react-router'),
31 | 'babel-polyfill': path.resolve(__dirname, '../node_modules/babel-polyfill'),
32 | 'isomorphic-fetch': path.resolve(__dirname, '../node_modules/isomorphic-fetch'),
33 | 'antd': path.resolve(__dirname, '../node_modules/antd'),
34 | }
35 | },
36 | module: {
37 | loaders: [
38 | {
39 | // 打包React代码需要引用Babel作为翻译器,并加入es2015, react等特性。
40 | test: /\.(js|jsx)$/,
41 | include: [path.resolve(__dirname, '../src')], //C:\workbench\git-repository\org.magicsoft\commons-react\ //path.resolve(__dirname, '../node_modules/commons-react'),
42 | loader: require.resolve('babel-loader'),
43 | query: {
44 | presets: ['es2015', 'react'],
45 | plugins: [
46 | ['import', { libraryName: 'antd', style: 'css' }] // `style: true` 会加载 less 文件
47 | ]
48 | }
49 | },
50 | {
51 | test: /\.css$/,
52 | loader: extractTextPlugin.extract('css-loader') // css打包。
53 | },
54 | {
55 | test: /\.(png|jpg|gif|svg)$/,
56 | loader: require.resolve('url-loader'),
57 | query: {
58 | limit: 10000, // 小于这个字节的图片会被打包成base64字符串。
59 | name: 'images/[name].[ext]?[hash:7]'
60 | }
61 | }
62 | ]
63 | },
64 | plugins: [
65 | extractTextPlugin, // 此插件的目的是将css单独打包成一个文件(不加的话css是会被打到js中的。)
66 | new HtmlWebpackPlugin({ //根据模板插入css/js等生成最终HTML
67 | filename: 'index.html', //生成的html存放路径,相对于 path
68 | template: 'src/index.html', // Load a custom template
69 | inject: true, //允许插件修改哪些内容,包括head与body
70 | hash: true, //为静态资源生成hash值
71 | // chunks: ['webpack-dev-server', 'index'] // 如果不指定这项,会把所有脚本都加载进来,指定了就只加载指定的脚本。
72 | }),
73 | // new CommonsChunkPlugin({
74 | // names: ['antd','react']
75 | // })
76 | ]
77 | }
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # React零基础入门
2 |
3 | ## 前言
4 | 此文档主要面向出生在前端(es6+,react,webpack,babel等)新手村的童鞋,主要目的是尽快让童鞋们从lv0尽快升级到lv10,走出新手村,探索更广阔的前端世界。内容较(te)为(bie)基础,请针对自身情况决定是否阅读。
5 | ***
6 | ## 目录
7 | 1. NodeJS安装;
8 | 2. 简单介绍npm与cnpm;
9 | 3. yarn简单介绍;
10 | 4. package.json文件的说明;
11 | 5. 总结
12 | ***
13 | ### 1.NodeJS安装
14 | NodeJS的安装没有技术可言,这里就不说了,而为什么要用Node,你就把Node想成一个使JS能够运行的一个解析器就好。
15 |
16 | > https://nodejs.org/en/download/ (Node.js官方安装包及源码下载地址)
17 |
18 | > http://www.cnblogs.com/yzadd/p/6547668.html (node详细安装过程及环境变量配置)
19 |
20 | ***
21 | ### 2.简单介绍npm与cnpm
22 | #### 2.1 npm介绍
23 | > http://registry.npmjs.org (npm地址)
24 |
25 | > http://npm.taobao.org (cnpm镜像地址)
26 |
27 | 1.npm(node package manager)是nodejs的包管理器,用于node插件管理(包括安装、卸载、管理依赖等);
28 |
29 | 2.使用npm安装插件:命令提示符执行```npm install [-g] [--save-dev]```
30 |
31 | ``````:node插件名称。
32 |
33 | 例:```npm install gulp-less --save-dev```
34 |
35 | -g:全局安装。将会安装在C:\Users\Administrator\AppData\Roaming\npm,并且写入系统环境变量;
36 |
37 | 不加-g :非全局安装:将会安装在当前定位目录;
38 |
39 | > 当你全局安装后可以通过命令行在任何地方调用它,本地安装将安装在定位目录的node_modules文件夹(存放第三方包)下。
40 |
41 | -save:将保存配置信息至package.json(package.json是nodejs项目配置文件);
42 |
43 | -dev:保存至package.json的devDependencies节点,不指定-dev将保存至dependencies节点;
44 |
45 | > 为什么要将配置保存至package.json?因为node插件包相对来说非常庞大,所以不加入版本管理,将配置信息写入package.json并将其加入版本管理,我们直接用命令提示符执行npm install(cnpm install||yarn install),则会根据package.json下载所有需要的包)。
46 |
47 | 3.使用npm卸载插件:```npm uninstall [-g] [--save-dev] ```。
48 |
49 | 4.使用npm更新插件:```npm update [-g] [--save-dev] ```。
50 |
51 | 5.更新全部插件:```npm update [--save-dev] ```。
52 |
53 | 6.查看npm帮助:```npm help ```。
54 |
55 | 7.查看当前目录已安装插件:```npm list```。
56 |
57 | #### 2.2 cnpm介绍
58 |
59 | 1.因为npm安装插件是从国外服务器 http://registry.npmjs.org 下载,受网络影响大,可能出现异常,淘宝团弄了个完整 npmjs.org 镜像(地址: http://npm.taobao.org ),来代替官方版本。
60 |
61 | 2.安装:命令提示符执行```npm install cnpm -g --registry=https://registry.npm.taobao.org```;
62 |
63 | > 注:cnpm跟npm用法完全一致,只是在执行命令时将npm改为cnpm。
64 |
65 | ***
66 | ### 3.yarn简单介绍
67 | > Yarn是Facebook发布了新的 node.js包管理器用以替代npm。使用yarn前需要保证git在全局可以找到,配置好git环境变量。(本人用的是webstorm,是使用中间配置的,需要重启软件)
68 |
69 | 1.其实 yarn 可以直接像装模块那样用 npm 装:```npm install -g yarn```;
70 |
71 | 2.yarn的安装依赖的方式不同于yarn,你需要执行以下命令来安装依赖:```yarn add react```(npm 为 npm install react);
72 |
73 | 3.更新一个依赖
74 |
75 | ```
76 | yarn upgrade [package]
77 |
78 | yarn upgrade [package]@[version]
79 |
80 | yarn upgrade [package]@[tag]
81 | ```
82 |
83 | 4.移除一个依赖
84 |
85 | ```yarn remove [package]```
86 |
87 | 5安装package.json中所有的依赖项
88 |
89 | ```yarn / yarn install```
90 |
91 | 6.yarn 更新所有的依赖包
92 |
93 | ```yarn upgrade-interactive```
94 |
95 | ***
96 | ### 4.package.json文件的说明
97 | 每个项目一般都有一个package.json文件,定义了这个项目所需要的各种模块,以及项目的配置信息。npm install命令根据这个配置文件(不光局限在npm和yarn。nodejs应用都生效),自动下载所需的模块,也就是配置项目所需的运行和开发环境。
98 |
99 | #### 1.概述
100 | package.json文件就是一个JSON对象,该对象的每一个成员就是当前项目的一项设置。比如name就是项目名称,version是版本···。
101 |
102 | package.json文件可以手工编写,也可以使用npm init命令自动生成。```$ npm init```在当前目录生成一个基本的package.json文件。有了package.json文件,直接使用```npm install```命令,就会在当前目录中安装所需要的模块。
103 |
104 | #### 2.scripts
105 | scripts指定了运行脚本命令的npm命令行缩写,比如start指定了运行npm run start(或yarn run start)时,所要执行的命令。
106 |
107 | #### 3.dependencies字段,devDependencies字段
108 | dependencies:指定了项目运行所依赖的模块,
109 |
110 | devDependencies:指定项目开发所需要的模块。
111 |
112 | > 它们都指向一个对象。该对象的各个成员,分别由模块名和对应的版本要求组成,表示依赖的模块及其版本范围。
113 |
114 | #### 4.bin字段
115 | bin项用来指定各个内部命令对应的可执行文件的位置。
116 |
117 | >所有node_modules/.bin/目录下的命令,都可以用npm run [命令]的格式运行。在命令行下,键入npm run,然后按tab键,就会显示所有可以使用的命令。
118 |
119 | #### 5.main字段
120 | main字段指定了加载的入口文件,require('moduleName')就会加载这个文件。这个字段的默认值是模块根目录下面的index.js。
121 |
122 | #### 6.config 字段
123 | config字段用于添加命令行的环境变量。
124 |
125 | #### 7.browser字段
126 | browser指定该模板供浏览器使用的版本。Browserify这样的浏览器打包工具,通过它就知道该打包那个文件。
127 |
128 | #### 8.engines 字段
129 | engines字段指明了该模块运行的平台,比如 Node 的某个版本或者浏览器,该字段也可以指定适用的npm版本。
130 |
131 | #### 9.man字段
132 | man用来指定当前模块的man文档的位置。
133 |
134 | #### 10.preferGlobal字段
135 | preferGlobal的值是布尔值,表示当用户不将该模块安装为全局模块时(即不用–global参数),要不要显示警告,表示该模块的本意就是安装为全局模块。
136 |
137 | #### 11.style字段
138 | style指定供浏览器使用时,样式文件所在的位置。样式文件打包工具parcelify,通过它知道样式文件的打包位置。
139 |
140 | ***
141 | ### 5.总结
142 | 学习React首先要知道它是什么东西,做什么用的,需要的工具和相关配置是做什么的,理解了这些离你自己可以写一个简单的React项目就不远了。
--------------------------------------------------------------------------------
/demo2/src/Tree.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 | import { Input,Tree } from 'antd';
3 | import 'whatwg-fetch';
4 | const Search = Input.Search;
5 | const TreeNode = Tree.TreeNode;
6 |
7 | class Tree1 extends React.Component {
8 | constructor(props) {
9 | super(props);
10 | this.state = {
11 | treeData: [],
12 | }
13 |
14 | this.onLoadData = this.onLoadData.bind(this)
15 | this.onSelect = this.onSelect.bind(this)
16 |
17 | }
18 |
19 | componentDidMount() {
20 | this.readFirst()
21 | }
22 |
23 | readFirst(){
24 | fetch('/api/mainframe/viewstate',
25 | ).then(response =>{
26 | console.log(response)
27 | return response.json()
28 | }
29 | ).then((response)=>{
30 | response.menuItems.map(function(item){
31 | item.title =item.text
32 | if(!item.items){
33 | item.isLeaf =true
34 | }
35 | // console.log(item)
36 | })
37 | this.state.treeData= response.menuItems
38 | this.Startrun();
39 | })
40 | }
41 | readJson(treeJson){
42 | // console.log(treeJson)
43 | treeJson.props.items.map(function(item1){
44 | item1.title =item1.text
45 | if(!item1.items){
46 | item1.isLeaf =true
47 | }
48 | })
49 | treeJson.props.dataRef.children = treeJson.props.items
50 | }
51 | /* readJson(treeJson){
52 | fetch('/api/mainframe/viewstate',
53 | ).then(response =>{
54 | //console.log(response)
55 | return response.json()
56 | }
57 | ).then((response)=>{
58 | response.menuItems.map(function(item){
59 | if(treeJson.props.title == item.text){
60 | item.items.map(function(item1){
61 | item1.title =item1.text
62 | if(!item1.items){
63 | item1.isLeaf =true
64 | }
65 | })
66 | treeJson.props.dataRef.children =item.items
67 | }
68 | })
69 |
70 | this.Startrun();
71 | })
72 | }*/
73 | onLoadData(treeNode){
74 | return (new Promise((resolve) => {
75 | if (treeNode.props.children) {
76 | resolve();
77 | return;
78 | }
79 | setTimeout(() => {
80 | // console.log(treeNode)
81 | this.readJson(treeNode)
82 | this.Startrun();
83 | resolve();
84 | }, 500);
85 | }));
86 | }
87 | Startrun(){
88 | this.setState({
89 | treeData: [...this.state.treeData],
90 | })
91 | }
92 | onSelect(electedKeys, e){
93 | var rvalue = [];
94 | if(e.selected){
95 | if(e.selectedNodes[0].props.dataRef.items){
96 | rvalue = e.selectedNodes[0].props.dataRef.items
97 | }else{
98 | rvalue.push(e.selectedNodes[0].props.dataRef)
99 | }
100 | this.props.callbackParent(rvalue);
101 | }
102 | return rvalue
103 | }
104 | renderTreeNodes(data){
105 | return data.map((item) => {
106 | if (item.children) {
107 | return (
108 |
109 | {this.renderTreeNodes(item.children)}
110 |
111 | );
112 | }
113 | return ;
114 | });
115 | }
116 | render() {
117 |
118 | return (
119 |
120 | console.log(value)}
124 | />
125 |
126 | {this.renderTreeNodes(this.state.treeData)}
127 |
128 |
129 | );
130 | }
131 | }
132 | export default Tree1;
--------------------------------------------------------------------------------
/demo3/src/registerServiceWorker.js:
--------------------------------------------------------------------------------
1 | // In production, we register a service worker to serve assets from local cache.
2 |
3 | // This lets the app load faster on subsequent visits in production, and gives
4 | // it offline capabilities. However, it also means that developers (and users)
5 | // will only see deployed updates on the "N+1" visit to a page, since previously
6 | // cached resources are updated in the background.
7 |
8 | // To learn more about the benefits of this model, read https://goo.gl/KwvDNy.
9 | // This link also includes instructions on opting out of this behavior.
10 |
11 | const isLocalhost = Boolean(
12 | window.location.hostname === 'localhost' ||
13 | // [::1] is the IPv6 localhost address.
14 | window.location.hostname === '[::1]' ||
15 | // 127.0.0.1/8 is considered localhost for IPv4.
16 | window.location.hostname.match(
17 | /^127(?:\.(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)){3}$/
18 | )
19 | );
20 |
21 | export default function register() {
22 | if (process.env.NODE_ENV === 'production' && 'serviceWorker' in navigator) {
23 | // The URL constructor is available in all browsers that support SW.
24 | const publicUrl = new URL(process.env.PUBLIC_URL, window.location);
25 | if (publicUrl.origin !== window.location.origin) {
26 | // Our service worker won't work if PUBLIC_URL is on a different origin
27 | // from what our page is served on. This might happen if a CDN is used to
28 | // serve assets; see https://github.com/facebookincubator/create-react-app/issues/2374
29 | return;
30 | }
31 |
32 | window.addEventListener('load', () => {
33 | const swUrl = `${process.env.PUBLIC_URL}/service-worker.js`;
34 |
35 | if (isLocalhost) {
36 | // This is running on localhost. Lets check if a service worker still exists or not.
37 | checkValidServiceWorker(swUrl);
38 | } else {
39 | // Is not local host. Just register service worker
40 | registerValidSW(swUrl);
41 | }
42 | });
43 | }
44 | }
45 |
46 | function registerValidSW(swUrl) {
47 | navigator.serviceWorker
48 | .register(swUrl)
49 | .then(registration => {
50 | registration.onupdatefound = () => {
51 | const installingWorker = registration.installing;
52 | installingWorker.onstatechange = () => {
53 | if (installingWorker.state === 'installed') {
54 | if (navigator.serviceWorker.controller) {
55 | // At this point, the old content will have been purged and
56 | // the fresh content will have been added to the cache.
57 | // It's the perfect time to display a "New content is
58 | // available; please refresh." message in your web app.
59 | console.log('New content is available; please refresh.');
60 | } else {
61 | // At this point, everything has been precached.
62 | // It's the perfect time to display a
63 | // "Content is cached for offline use." message.
64 | console.log('Content is cached for offline use.');
65 | }
66 | }
67 | };
68 | };
69 | })
70 | .catch(error => {
71 | console.error('Error during service worker registration:', error);
72 | });
73 | }
74 |
75 | function checkValidServiceWorker(swUrl) {
76 | // Check if the service worker can be found. If it can't reload the page.
77 | fetch(swUrl)
78 | .then(response => {
79 | // Ensure service worker exists, and that we really are getting a JS file.
80 | if (
81 | response.status === 404 ||
82 | response.headers.get('content-type').indexOf('javascript') === -1
83 | ) {
84 | // No service worker found. Probably a different app. Reload the page.
85 | navigator.serviceWorker.ready.then(registration => {
86 | registration.unregister().then(() => {
87 | window.location.reload();
88 | });
89 | });
90 | } else {
91 | // Service worker found. Proceed as normal.
92 | registerValidSW(swUrl);
93 | }
94 | })
95 | .catch(() => {
96 | console.log(
97 | 'No internet connection found. App is running in offline mode.'
98 | );
99 | });
100 | }
101 |
102 | export function unregister() {
103 | if ('serviceWorker' in navigator) {
104 | navigator.serviceWorker.ready.then(registration => {
105 | registration.unregister();
106 | });
107 | }
108 | }
109 |
--------------------------------------------------------------------------------
/demo1/1.入门基础(demo1解释).md:
--------------------------------------------------------------------------------
1 | # 1.基础入门(demo1解释)
2 |
3 | ## 前言
4 | 该文档主要依照demo1讲解相关结构内容,还有一个基础的react项目都有些什么。
5 | ***
6 | ## 目录
7 | 1. 简单介绍webpack;
8 | 2. React项目的结构;
9 | 3. ES6导出的两种方法区别;
10 | 4. React中state与props介绍与比较
11 | 5. ES6(ECMAScript2015)
12 | ***
13 | ### 1.webpack的介绍
14 | > webpack的安装就不详细讲解了,详细请参考 ( http://www.jianshu.com/p/42e11515c10f )
15 |
16 | 我认为WebPack就是分析你的项目结构,找到JavaScript模块以及其它的一些浏览器不能直接运行的拓展语言,并将其转换和打包为合适的格式供浏览器使用。
17 |
18 | 我们以demo1中的demo1\webpack\webpack.config.js(webpack配置文件)|webpack.dev.config.js(webpack开发环境配置)|webpack.prod.config.js(webpack生产环境配置)为例一步步讲解。
19 |
20 | **entry**:是打包(计算依赖)的唯一入口文件,即从哪个文件开始进行查找打包。
21 |
22 | >path.resolve由于该方法属于path模块,使用前需要引入path模块``` (const path= require(“path”)) ``` ;现在这种用法是把它作为一个序列的cd命令shell,在demo1\webpack\webpack.config.js就是在../src目录下查找Index.jsx文件的作用。
23 |
24 | **output** 该选项影响编译输出
25 |
26 | **output.filename**:编译打包后输出文件的文件名,[name]指的是来源entry中的文件名
27 |
28 | **resolve** :该选项影响解析模块
29 |
30 | **resolve.alias** :将配置模块名与模块文件对应上
31 |
32 | **resolve.extensions** :解析模块的拓展名的数组(哪些文件进行解析,简单来讲就是不用输入拓展名也可以进行解析)。默认: ["", ".webpack.js", ".web.js", ".js"]
33 |
34 | **module.loaders** 自动引用的加载器的数组.
35 |
36 | **plugins** 给编译器添加额外的插件.
37 |
38 | **注“__dirname”是node.js中的一个全局变量,它指向当前执行脚本所在的目录。**
39 |
40 | > npm的start命令是一个特殊的脚本名称,其特殊性表现在,在命令行中使用npm start就可以执行其对于的命令,如果对应的此脚本名称不是start,想要在命令行中运行时,需要这样用``` npm run {script name} ```如
41 | ``` npm run build ```
42 |
43 | ***
44 | ### 2.React项目的结构
45 |
46 | |-demo1 //项目名称
47 |
48 | |---node_modules //第三方插件库(在package.json中配置好在用 yarn install 自动下载)
49 |
50 | |---src //存放项目文件 如Index.jsx等
51 |
52 | |---webpack //webpack配置文件目录(上面讲到,这里就不详细讲解了)
53 |
54 | |---package.json //定义了这个项目所需要的各种模块,以及项目的配置信息(比如名称、版本、许可证等元数据)(在零基础入门讲过)
55 |
56 | |---server.js //服务器配置
57 |
58 | ***
59 | ### 3.ES6导出的两种方法区别;
60 | > React中使用export导出类可以有两种方法
61 |
62 | #### 1. export default classname(一个文件中只有一个report default)
63 |
64 | 这种导出方式与``` export default class classname extends React.class ```相同
65 |
66 | 在其他文件中引用时采取方式:``` import classname form path ```
67 |
68 | #### 2. export {classname1,classname2} (可以多个同时引)
69 |
70 | 在其他文件中引用时采用如下方式
71 |
72 | import {classname1,classname2} from path
73 |
74 | import {classname1} //注意引用一个类时也要加上{}
75 |
76 |
77 | ***
78 | ### 4.React中state与props介绍
79 | > 详细介绍请查看( http://www.cnblogs.com/ZSG-DoBestMe/p/5293457.html )
80 |
81 | **props**:一般用于父组件向子组件通信,在组件之间通信使用。
82 |
83 | **state**:一般用于组件内部的状态维护,更新组建内部的数据,状态,更新子组件的props等。
84 |
85 | ***
86 | ### 5.ES6(ECMAScript2015)
87 | > ECMAScript 6(以下简称ES6)是JavaScript语言的下一代标准。因为当前版本的ES6是在2015年发布的,所以又称ECMAScript 2015。
88 |
89 | > http://babeljs.io/learn-es2015/ (Babel官网)
90 |
91 | > http://es6.ruanyifeng.com/ (ECMAScript入门 作者:阮一峰)
92 |
93 | > https://facebook.github.io/react/docs/components-and-props.html (React文档)
94 |
95 | > http://caibaojian.com/es6/object.html (ECMAScript 6拓展)
96 |
97 | 在我们正式讲解ES6语法之前,我们得先了解下Babel。Babel是一个广泛使用的ES6转码器,可以将ES6代码转为ES5代码,从而在现有环境执行。大家可以选择自己习惯的工具来使用使用Babel,具体过程可直接在Babel官网查看 http://babeljs.io/learn-es2015/
98 |
99 | #### 最常用的ES6特性
100 | ```
101 | let, const, class, extends, super, arrow functions,
102 | template string,destructuring, default, rest arguments
103 | ```
104 | 这些是ES6最常用的几个语法,我会用最通俗易懂的语言来讲解它们。
105 |
106 | ##### let, const
107 | 这两个的用途与var类似,都是用来声明变量的,但在实际运用中他俩都有各自的特殊用途。
108 |
109 | ES5只有全局作用域和函数作用域,没有块级作用域,这带来很多不合理的场景.
110 |
111 | 而let则实际上为JavaScript新增了块级作用域。用它所声明的变量,只在let命令所在的代码块内有效。
112 |
113 | const也用来声明变量,但是声明的是常量。一旦声明,常量的值就不能改变。当我们尝试去改变用const声明的常量时,浏览器就会报错。
114 |
115 | const有一个很好的应用场景,就是当我们引用第三方库的时声明的变量,用const来声明可以避免未来不小心重命名而导致出现bug:``` const monent = require('moment') ```
116 |
117 | ##### class, extends, super
118 | ES6提供了更接近传统语言的写法,引入了Class(类)这个概念。新的class写法让对象原型的写法更加清晰、更像面向对象编程的语法,也更加通俗易懂。
119 |
120 | class关键字用来定义类
121 |
122 | extends关键字用来实现继承
123 |
124 | super关键字,它指代父类的实例(即父类的this对象)子类必须在constructor方法中调用super方法,否则新建实例时会报错。这是因为子类没有自己的this对象,而是继承父类的this对象,然后对其进行加工。如果不调用super方法,子类就得不到this对象。
125 |
126 |
127 | ##### arrow function(=>)
128 | 用它来写function比原来的写法要简洁清晰很多,如果方程比较复杂,则需要用{}把代码包起来。
129 |
130 | ```
131 | 例1:
132 | --------------------------------------
133 | function(i){ return i + 1; } //ES5
134 | (i) => i + 1 //ES6
135 | ---------------------------------------
136 | 例2:
137 | ---------------------------------------
138 | function(x, y) {
139 | x++;
140 | y--;
141 | return x + y;
142 | } //es5
143 | (x, y) => {x++; y--; return x+y} //es6
144 | ----------------------------------------
145 | 例3:
146 | ----------------------------------------
147 | class Animal {
148 | constructor(){
149 | this.type = 'animal'
150 | }
151 | says(say){
152 | setTimeout( () => {
153 | console.log(this.type + ' says ' + say)
154 | }, 1000) } }
155 | var animal = new Animal()
156 | animal.says('hi') //animal says hi
157 |
158 | ```
159 |
160 | 当我们使用箭头函数时,函数体内的this对象,就是定义时所在的对象,而不是使用时所在的对象。
161 | 并不是因为箭头函数内部有绑定this的机制,实际原因是箭头函数根本没有自己的this,它的this是继承外面的,因此内部的this就是外层代码块的this。
--------------------------------------------------------------------------------
/demo2/src/CenterTable.jsx:
--------------------------------------------------------------------------------
1 | import React from 'react'
2 | import { DatePicker,Select ,Table,Row, Col,Button ,Input } from 'antd';
3 | import './css/index.css'
4 | const { MonthPicker, RangePicker } = DatePicker;
5 |
6 | const Option = Select.Option;
7 | function onChange(date, dateString) {
8 | console.log(date, dateString);
9 | }
10 | function handleChange(value) {
11 | console.log(`selected ${value}`);
12 | }
13 |
14 | function handleBlur() {
15 | console.log('blur');
16 | }
17 |
18 | function handleFocus() {
19 | console.log('focus');
20 | }
21 | const columns = [{
22 | title: 'Name',
23 | dataIndex: 'name',
24 | render: text => {text} ,
25 | }, {
26 | title: 'Age',
27 | dataIndex: 'age',
28 | }, {
29 | title: 'Address',
30 | dataIndex: 'address',
31 | }];
32 | const data = [{
33 | key: '1',
34 | name: 'John Brown',
35 | age: 32,
36 | address: 'New York No. 1 Lake Park',
37 | }, {
38 | key: '2',
39 | name: 'Jim Green',
40 | age: 42,
41 | address: 'London No. 1 Lake Park',
42 | }, {
43 | key: '3',
44 | name: 'Joe Black',
45 | age: 32,
46 | address: 'Sidney No. 1 Lake Park',
47 | }, {
48 | key: '4',
49 | name: 'Disabled User',
50 | age: 99,
51 | address: 'Sidney No. 1 Lake Park',
52 | }];
53 |
54 | // rowSelection object indicates the need for row selection
55 | const rowSelection = {
56 | onChange: (selectedRowKeys, selectedRows) => {
57 | console.log(`selectedRowKeys: ${selectedRowKeys}`, 'selectedRows: ', selectedRows);
58 | },
59 | getCheckboxProps: record => ({
60 | // disabled: record.name === 'Disabled User',
61 | }),
62 | };
63 |
64 | class CenterTable extends React.Component{
65 | constructor(props) {
66 | super(props);
67 | }
68 |
69 | render(){
70 | return(
71 |
72 |
73 |
74 |
75 | 在职干部库
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 | 姓名:
84 |
85 |
86 |
87 |
88 |
89 |
90 |
91 |
92 |
93 | 性别:
94 |
95 |
96 |
97 | 男
98 | 女
99 |
100 |
101 |
102 |
103 |
104 |
105 |
106 |
107 |
108 |
109 | 出生日期:
110 |
111 |
112 |
113 |
114 |
115 |
116 |
117 |
118 |
119 | 籍贯:
120 |
121 |
122 | option.props.children.toLowerCase().indexOf(input.toLowerCase()) >= 0}
131 | >
132 | 山西
133 | 北京
134 | 上海
135 |
136 |
137 |
138 |
139 |
140 |
141 |
142 |
143 |
144 | 新建
145 | 删除
146 | 刷新
147 | 加入干部
148 |
149 |
150 |
151 |
152 |
153 |
154 |
155 |
156 |
157 | )
158 | }
159 | };
160 | export default CenterTable
--------------------------------------------------------------------------------
/demo3/.idea/workspace.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 |
89 |
90 |
91 |
92 |
93 |
94 |
95 |
96 |
97 |
98 |
99 |
100 |
101 |
102 |
103 |
104 |
105 |
106 |
107 |
108 |
109 |
110 |
111 |
112 |
113 |
114 |
115 |
116 |
117 |
118 |
119 |
120 |
121 |
122 |
123 |
124 |
125 |
126 |
127 |
128 | true
129 |
130 | false
131 | true
132 | true
133 |
134 |
135 | true
136 | DEFINITION_ORDER
137 |
138 |
139 |
140 |
141 |
142 |
143 |
144 |
145 |
146 |
147 |
148 |
149 |
150 |
151 |
152 |
153 |
154 |
155 |
156 |
157 |
158 |
159 |
160 |
161 |
162 |
163 |
164 |
165 |
166 |
167 |
168 |
169 |
170 |
171 |
172 |
173 |
174 |
175 |
176 |
177 |
178 |
179 |
180 |
181 |
182 |
183 |
184 |
185 |
186 |
187 |
188 |
189 |
190 |
191 |
192 |
193 |
194 |
195 |
196 |
197 |
198 |
199 |
200 |
201 |
202 |
203 |
204 |
205 |
206 |
207 |
208 |
209 |
210 |
211 |
212 |
213 |
214 | 1509936020512
215 |
216 |
217 | 1509936020512
218 |
219 |
220 |
221 |
222 |
223 |
224 |
225 |
226 |
227 |
228 |
229 |
230 |
231 |
232 |
233 |
234 |
235 |
236 |
237 |
238 |
239 |
240 |
241 |
242 |
243 |
244 |
245 |
246 |
247 |
248 |
249 |
250 |
251 |
252 |
253 |
254 |
255 |
256 |
257 |
258 |
259 |
260 |
261 |
262 |
263 |
264 |
265 |
266 |
267 |
268 |
269 |
270 |
271 |
272 |
273 |
274 |
275 |
276 |
277 |
278 |
279 |
280 |
281 |
282 |
283 |
284 |
285 |
286 |
287 |
288 |
289 |
290 |
291 |
292 |
293 |
294 |
295 |
296 |
297 |
298 |
299 |
300 |
301 |
302 |
303 |
304 |
305 |
306 |
307 |
308 |
309 |
310 |
311 |
312 |
313 |
314 |
315 |
316 |
317 |
318 |
319 |
320 |
321 |
322 |
323 |
324 |
325 |
326 |
327 |
328 |
329 |
330 |
331 |
332 |
333 |
334 |
335 |
336 |
337 |
338 |
339 |
340 |
341 |
342 |
343 |
344 |
345 |
346 |
347 |
348 |
349 |
350 |
351 |
352 |
353 |
354 |
355 |
356 |
357 |
358 |
359 |
360 |
361 |
362 |
363 |
364 |
365 |
366 |
367 |
368 |
369 |
370 |
371 |
372 |
373 |
374 |
--------------------------------------------------------------------------------
/demo3/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 | - [Formatting Code Automatically](#formatting-code-automatically)
21 | - [Changing the Page ``](#changing-the-page-title)
22 | - [Installing a Dependency](#installing-a-dependency)
23 | - [Importing a Component](#importing-a-component)
24 | - [Code Splitting](#code-splitting)
25 | - [Adding a Stylesheet](#adding-a-stylesheet)
26 | - [Post-Processing CSS](#post-processing-css)
27 | - [Adding a CSS Preprocessor (Sass, Less etc.)](#adding-a-css-preprocessor-sass-less-etc)
28 | - [Adding Images, Fonts, and Files](#adding-images-fonts-and-files)
29 | - [Using the `public` Folder](#using-the-public-folder)
30 | - [Changing the HTML](#changing-the-html)
31 | - [Adding Assets Outside of the Module System](#adding-assets-outside-of-the-module-system)
32 | - [When to Use the `public` Folder](#when-to-use-the-public-folder)
33 | - [Using Global Variables](#using-global-variables)
34 | - [Adding Bootstrap](#adding-bootstrap)
35 | - [Using a Custom Theme](#using-a-custom-theme)
36 | - [Adding Flow](#adding-flow)
37 | - [Adding Custom Environment Variables](#adding-custom-environment-variables)
38 | - [Referencing Environment Variables in the HTML](#referencing-environment-variables-in-the-html)
39 | - [Adding Temporary Environment Variables In Your Shell](#adding-temporary-environment-variables-in-your-shell)
40 | - [Adding Development Environment Variables In `.env`](#adding-development-environment-variables-in-env)
41 | - [Can I Use Decorators?](#can-i-use-decorators)
42 | - [Integrating with an API Backend](#integrating-with-an-api-backend)
43 | - [Node](#node)
44 | - [Ruby on Rails](#ruby-on-rails)
45 | - [Proxying API Requests in Development](#proxying-api-requests-in-development)
46 | - ["Invalid Host Header" Errors After Configuring Proxy](#invalid-host-header-errors-after-configuring-proxy)
47 | - [Configuring the Proxy Manually](#configuring-the-proxy-manually)
48 | - [Configuring a WebSocket Proxy](#configuring-a-websocket-proxy)
49 | - [Using HTTPS in Development](#using-https-in-development)
50 | - [Generating Dynamic ` ` Tags on the Server](#generating-dynamic-meta-tags-on-the-server)
51 | - [Pre-Rendering into Static HTML Files](#pre-rendering-into-static-html-files)
52 | - [Injecting Data from the Server into the Page](#injecting-data-from-the-server-into-the-page)
53 | - [Running Tests](#running-tests)
54 | - [Filename Conventions](#filename-conventions)
55 | - [Command Line Interface](#command-line-interface)
56 | - [Version Control Integration](#version-control-integration)
57 | - [Writing Tests](#writing-tests)
58 | - [Testing Components](#testing-components)
59 | - [Using Third Party Assertion Libraries](#using-third-party-assertion-libraries)
60 | - [Initializing Test Environment](#initializing-test-environment)
61 | - [Focusing and Excluding Tests](#focusing-and-excluding-tests)
62 | - [Coverage Reporting](#coverage-reporting)
63 | - [Continuous Integration](#continuous-integration)
64 | - [Disabling jsdom](#disabling-jsdom)
65 | - [Snapshot Testing](#snapshot-testing)
66 | - [Editor Integration](#editor-integration)
67 | - [Developing Components in Isolation](#developing-components-in-isolation)
68 | - [Getting Started with Storybook](#getting-started-with-storybook)
69 | - [Getting Started with Styleguidist](#getting-started-with-styleguidist)
70 | - [Making a Progressive Web App](#making-a-progressive-web-app)
71 | - [Opting Out of Caching](#opting-out-of-caching)
72 | - [Offline-First Considerations](#offline-first-considerations)
73 | - [Progressive Web App Metadata](#progressive-web-app-metadata)
74 | - [Analyzing the Bundle Size](#analyzing-the-bundle-size)
75 | - [Deployment](#deployment)
76 | - [Static Server](#static-server)
77 | - [Other Solutions](#other-solutions)
78 | - [Serving Apps with Client-Side Routing](#serving-apps-with-client-side-routing)
79 | - [Building for Relative Paths](#building-for-relative-paths)
80 | - [Azure](#azure)
81 | - [Firebase](#firebase)
82 | - [GitHub Pages](#github-pages)
83 | - [Heroku](#heroku)
84 | - [Netlify](#netlify)
85 | - [Now](#now)
86 | - [S3 and CloudFront](#s3-and-cloudfront)
87 | - [Surge](#surge)
88 | - [Advanced Configuration](#advanced-configuration)
89 | - [Troubleshooting](#troubleshooting)
90 | - [`npm start` doesn’t detect changes](#npm-start-doesnt-detect-changes)
91 | - [`npm test` hangs on macOS Sierra](#npm-test-hangs-on-macos-sierra)
92 | - [`npm run build` exits too early](#npm-run-build-exits-too-early)
93 | - [`npm run build` fails on Heroku](#npm-run-build-fails-on-heroku)
94 | - [`npm run build` fails to minify](#npm-run-build-fails-to-minify)
95 | - [Moment.js locales are missing](#momentjs-locales-are-missing)
96 | - [Something Missing?](#something-missing)
97 |
98 | ## Updating to New Releases
99 |
100 | Create React App is divided into two packages:
101 |
102 | * `create-react-app` is a global command-line utility that you use to create new projects.
103 | * `react-scripts` is a development dependency in the generated projects (including this one).
104 |
105 | You almost never need to update `create-react-app` itself: it delegates all the setup to `react-scripts`.
106 |
107 | 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.
108 |
109 | 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.
110 |
111 | 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.
112 |
113 | We commit to keeping the breaking changes minimal so you can upgrade `react-scripts` painlessly.
114 |
115 | ## Sending Feedback
116 |
117 | We are always open to [your feedback](https://github.com/facebookincubator/create-react-app/issues).
118 |
119 | ## Folder Structure
120 |
121 | After creation, your project should look like this:
122 |
123 | ```
124 | my-app/
125 | README.md
126 | node_modules/
127 | package.json
128 | public/
129 | index.html
130 | favicon.ico
131 | src/
132 | App.css
133 | App.js
134 | App.test.js
135 | index.css
136 | index.js
137 | logo.svg
138 | ```
139 |
140 | For the project to build, **these files must exist with exact filenames**:
141 |
142 | * `public/index.html` is the page template;
143 | * `src/index.js` is the JavaScript entry point.
144 |
145 | You can delete or rename the other files.
146 |
147 | You may create subdirectories inside `src`. For faster rebuilds, only files inside `src` are processed by Webpack.
148 | You need to **put any JS and CSS files inside `src`**, otherwise Webpack won’t see them.
149 |
150 | Only files inside `public` can be used from `public/index.html`.
151 | Read instructions below for using assets from JavaScript and HTML.
152 |
153 | You can, however, create more top-level directories.
154 | They will not be included in the production build so you can use them for things like documentation.
155 |
156 | ## Available Scripts
157 |
158 | In the project directory, you can run:
159 |
160 | ### `npm start`
161 |
162 | Runs the app in the development mode.
163 | Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
164 |
165 | The page will reload if you make edits.
166 | You will also see any lint errors in the console.
167 |
168 | ### `npm test`
169 |
170 | Launches the test runner in the interactive watch mode.
171 | See the section about [running tests](#running-tests) for more information.
172 |
173 | ### `npm run build`
174 |
175 | Builds the app for production to the `build` folder.
176 | It correctly bundles React in production mode and optimizes the build for the best performance.
177 |
178 | The build is minified and the filenames include the hashes.
179 | Your app is ready to be deployed!
180 |
181 | See the section about [deployment](#deployment) for more information.
182 |
183 | ### `npm run eject`
184 |
185 | **Note: this is a one-way operation. Once you `eject`, you can’t go back!**
186 |
187 | 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.
188 |
189 | 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.
190 |
191 | 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.
192 |
193 | ## Supported Language Features and Polyfills
194 |
195 | This project supports a superset of the latest JavaScript standard.
196 | In addition to [ES6](https://github.com/lukehoban/es6features) syntax features, it also supports:
197 |
198 | * [Exponentiation Operator](https://github.com/rwaldron/exponentiation-operator) (ES2016).
199 | * [Async/await](https://github.com/tc39/ecmascript-asyncawait) (ES2017).
200 | * [Object Rest/Spread Properties](https://github.com/sebmarkbage/ecmascript-rest-spread) (stage 3 proposal).
201 | * [Dynamic import()](https://github.com/tc39/proposal-dynamic-import) (stage 3 proposal)
202 | * [Class Fields and Static Properties](https://github.com/tc39/proposal-class-public-fields) (part of stage 3 proposal).
203 | * [JSX](https://facebook.github.io/react/docs/introducing-jsx.html) and [Flow](https://flowtype.org/) syntax.
204 |
205 | Learn more about [different proposal stages](https://babeljs.io/docs/plugins/#presets-stage-x-experimental-presets-).
206 |
207 | While we recommend using 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.
208 |
209 | Note that **the project only includes a few ES6 [polyfills](https://en.wikipedia.org/wiki/Polyfill)**:
210 |
211 | * [`Object.assign()`](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Object/assign) via [`object-assign`](https://github.com/sindresorhus/object-assign).
212 | * [`Promise`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) via [`promise`](https://github.com/then/promise).
213 | * [`fetch()`](https://developer.mozilla.org/en/docs/Web/API/Fetch_API) via [`whatwg-fetch`](https://github.com/github/fetch).
214 |
215 | 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.
216 |
217 | ## Syntax Highlighting in the Editor
218 |
219 | 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.
220 |
221 | ## Displaying Lint Output in the Editor
222 |
223 | >Note: this feature is available with `react-scripts@0.2.0` and higher.
224 | >It also only works with npm 3 or higher.
225 |
226 | Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.
227 |
228 | 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.
229 |
230 | You would need to install an ESLint plugin for your editor first. Then, add a file called `.eslintrc` to the project root:
231 |
232 | ```js
233 | {
234 | "extends": "react-app"
235 | }
236 | ```
237 |
238 | Now your editor should report the linting warnings.
239 |
240 | Note that even if you edit your `.eslintrc` file further, these changes will **only affect the editor integration**. They won’t affect the terminal and in-browser lint output. This is because Create React App intentionally provides a minimal set of rules that find common mistakes.
241 |
242 | If you want to enforce a coding style for your project, consider using [Prettier](https://github.com/jlongster/prettier) instead of ESLint style rules.
243 |
244 | ## Debugging in the Editor
245 |
246 | **This feature is currently only supported by [Visual Studio Code](https://code.visualstudio.com) and [WebStorm](https://www.jetbrains.com/webstorm/).**
247 |
248 | Visual Studio Code and WebStorm support 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.
249 |
250 | ### Visual Studio Code
251 |
252 | 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.
253 |
254 | Then add the block below to your `launch.json` file and put it inside the `.vscode` folder in your app’s root directory.
255 |
256 | ```json
257 | {
258 | "version": "0.2.0",
259 | "configurations": [{
260 | "name": "Chrome",
261 | "type": "chrome",
262 | "request": "launch",
263 | "url": "http://localhost:3000",
264 | "webRoot": "${workspaceRoot}/src",
265 | "sourceMapPathOverrides": {
266 | "webpack:///src/*": "${webRoot}/*"
267 | }
268 | }]
269 | }
270 | ```
271 | >Note: the URL may be different if you've made adjustments via the [HOST or PORT environment variables](#advanced-configuration).
272 |
273 | 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.
274 |
275 | Having problems with VS Code Debugging? Please see their [troubleshooting guide](https://github.com/Microsoft/vscode-chrome-debug/blob/master/README.md#troubleshooting).
276 |
277 | ### WebStorm
278 |
279 | You would need to have [WebStorm](https://www.jetbrains.com/webstorm/) and [JetBrains IDE Support](https://chrome.google.com/webstore/detail/jetbrains-ide-support/hmhgeddbohgjknpmjagkdomcpobmllji) Chrome extension installed.
280 |
281 | In the WebStorm menu `Run` select `Edit Configurations...`. Then click `+` and select `JavaScript Debug`. Paste `http://localhost:3000` into the URL field and save the configuration.
282 |
283 | >Note: the URL may be different if you've made adjustments via the [HOST or PORT environment variables](#advanced-configuration).
284 |
285 | Start your app by running `npm start`, then press `^D` on macOS or `F9` on Windows and Linux or click the green debug icon to start debugging in WebStorm.
286 |
287 | The same way you can debug your application in IntelliJ IDEA Ultimate, PhpStorm, PyCharm Pro, and RubyMine.
288 |
289 | ## Formatting Code Automatically
290 |
291 | Prettier is an opinionated code formatter with support for JavaScript, CSS and JSON. With Prettier you can format the code you write automatically to ensure a code style within your project. See the [Prettier's GitHub page](https://github.com/prettier/prettier) for more information, and look at this [page to see it in action](https://prettier.github.io/prettier/).
292 |
293 | To format our code whenever we make a commit in git, we need to install the following dependencies:
294 |
295 | ```sh
296 | npm install --save husky lint-staged prettier
297 | ```
298 |
299 | Alternatively you may use `yarn`:
300 |
301 | ```sh
302 | yarn add husky lint-staged prettier
303 | ```
304 |
305 | * `husky` makes it easy to use githooks as if they are npm scripts.
306 | * `lint-staged` allows us to run scripts on staged files in git. See this [blog post about lint-staged to learn more about it](https://medium.com/@okonetchnikov/make-linting-great-again-f3890e1ad6b8).
307 | * `prettier` is the JavaScript formatter we will run before commits.
308 |
309 | Now we can make sure every file is formatted correctly by adding a few lines to the `package.json` in the project root.
310 |
311 | Add the following line to `scripts` section:
312 |
313 | ```diff
314 | "scripts": {
315 | + "precommit": "lint-staged",
316 | "start": "react-scripts start",
317 | "build": "react-scripts build",
318 | ```
319 |
320 | Next we add a 'lint-staged' field to the `package.json`, for example:
321 |
322 | ```diff
323 | "dependencies": {
324 | // ...
325 | },
326 | + "lint-staged": {
327 | + "src/**/*.{js,jsx,json,css}": [
328 | + "prettier --single-quote --write",
329 | + "git add"
330 | + ]
331 | + },
332 | "scripts": {
333 | ```
334 |
335 | Now, whenever you make a commit, Prettier will format the changed files automatically. You can also run `./node_modules/.bin/prettier --single-quote --write "src/**/*.{js,jsx}"` to format your entire project for the first time.
336 |
337 | Next you might want to integrate Prettier in your favorite editor. Read the section on [Editor Integration](https://github.com/prettier/prettier#editor-integration) on the Prettier GitHub page.
338 |
339 | ## Changing the Page ``
340 |
341 | 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.
342 |
343 | 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.
344 |
345 | 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.
346 |
347 | 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).
348 |
349 | ## Installing a Dependency
350 |
351 | 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`:
352 |
353 | ```sh
354 | npm install --save react-router
355 | ```
356 |
357 | Alternatively you may use `yarn`:
358 |
359 | ```sh
360 | yarn add react-router
361 | ```
362 |
363 | This works for any library, not just `react-router`.
364 |
365 | ## Importing a Component
366 |
367 | This project setup supports ES6 modules thanks to Babel.
368 | 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.
369 |
370 | For example:
371 |
372 | ### `Button.js`
373 |
374 | ```js
375 | import React, { Component } from 'react';
376 |
377 | class Button extends Component {
378 | render() {
379 | // ...
380 | }
381 | }
382 |
383 | export default Button; // Don’t forget to use export default!
384 | ```
385 |
386 | ### `DangerButton.js`
387 |
388 |
389 | ```js
390 | import React, { Component } from 'react';
391 | import Button from './Button'; // Import a component from another file
392 |
393 | class DangerButton extends Component {
394 | render() {
395 | return ;
396 | }
397 | }
398 |
399 | export default DangerButton;
400 | ```
401 |
402 | 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.
403 |
404 | 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'`.
405 |
406 | 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.
407 |
408 | Learn more about ES6 modules:
409 |
410 | * [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)
411 | * [Exploring ES6: Modules](http://exploringjs.com/es6/ch_modules.html)
412 | * [Understanding ES6: Modules](https://leanpub.com/understandinges6/read#leanpub-auto-encapsulating-code-with-modules)
413 |
414 | ## Code Splitting
415 |
416 | Instead of downloading the entire app before users can use it, code splitting allows you to split your code into small chunks which you can then load on demand.
417 |
418 | This project setup supports code splitting via [dynamic `import()`](http://2ality.com/2017/01/import-operator.html#loading-code-on-demand). Its [proposal](https://github.com/tc39/proposal-dynamic-import) is in stage 3. The `import()` function-like form takes the module name as an argument and returns a [`Promise`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) which always resolves to the namespace object of the module.
419 |
420 | Here is an example:
421 |
422 | ### `moduleA.js`
423 |
424 | ```js
425 | const moduleA = 'Hello';
426 |
427 | export { moduleA };
428 | ```
429 | ### `App.js`
430 |
431 | ```js
432 | import React, { Component } from 'react';
433 |
434 | class App extends Component {
435 | handleClick = () => {
436 | import('./moduleA')
437 | .then(({ moduleA }) => {
438 | // Use moduleA
439 | })
440 | .catch(err => {
441 | // Handle failure
442 | });
443 | };
444 |
445 | render() {
446 | return (
447 |
448 | Load
449 |
450 | );
451 | }
452 | }
453 |
454 | export default App;
455 | ```
456 |
457 | This will make `moduleA.js` and all its unique dependencies as a separate chunk that only loads after the user clicks the 'Load' button.
458 |
459 | You can also use it with `async` / `await` syntax if you prefer it.
460 |
461 | ### With React Router
462 |
463 | If you are using React Router check out [this tutorial](http://serverless-stack.com/chapters/code-splitting-in-create-react-app.html) on how to use code splitting with it. You can find the companion GitHub repository [here](https://github.com/AnomalyInnovations/serverless-stack-demo-client/tree/code-splitting-in-create-react-app).
464 |
465 | ## Adding a Stylesheet
466 |
467 | This project setup uses [Webpack](https://webpack.js.org/) 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**:
468 |
469 | ### `Button.css`
470 |
471 | ```css
472 | .Button {
473 | padding: 20px;
474 | }
475 | ```
476 |
477 | ### `Button.js`
478 |
479 | ```js
480 | import React, { Component } from 'react';
481 | import './Button.css'; // Tell Webpack that Button.js uses these styles
482 |
483 | class Button extends Component {
484 | render() {
485 | // You can use them as regular CSS styles
486 | return
;
487 | }
488 | }
489 | ```
490 |
491 | **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.
492 |
493 | 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.
494 |
495 | 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.
496 |
497 | ## Post-Processing CSS
498 |
499 | 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.
500 |
501 | For example, this:
502 |
503 | ```css
504 | .App {
505 | display: flex;
506 | flex-direction: row;
507 | align-items: center;
508 | }
509 | ```
510 |
511 | becomes this:
512 |
513 | ```css
514 | .App {
515 | display: -webkit-box;
516 | display: -ms-flexbox;
517 | display: flex;
518 | -webkit-box-orient: horizontal;
519 | -webkit-box-direction: normal;
520 | -ms-flex-direction: row;
521 | flex-direction: row;
522 | -webkit-box-align: center;
523 | -ms-flex-align: center;
524 | align-items: center;
525 | }
526 | ```
527 |
528 | If you need to disable autoprefixing for some reason, [follow this section](https://github.com/postcss/autoprefixer#disabling).
529 |
530 | ## Adding a CSS Preprocessor (Sass, Less etc.)
531 |
532 | 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)).
533 |
534 | 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.
535 |
536 | First, let’s install the command-line interface for Sass:
537 |
538 | ```sh
539 | npm install --save node-sass-chokidar
540 | ```
541 |
542 | Alternatively you may use `yarn`:
543 |
544 | ```sh
545 | yarn add node-sass-chokidar
546 | ```
547 |
548 | Then in `package.json`, add the following lines to `scripts`:
549 |
550 | ```diff
551 | "scripts": {
552 | + "build-css": "node-sass-chokidar src/ -o src/",
553 | + "watch-css": "npm run build-css && node-sass-chokidar src/ -o src/ --watch --recursive",
554 | "start": "react-scripts start",
555 | "build": "react-scripts build",
556 | "test": "react-scripts test --env=jsdom",
557 | ```
558 |
559 | >Note: To use a different preprocessor, replace `build-css` and `watch-css` commands according to your preprocessor’s documentation.
560 |
561 | 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.
562 |
563 | 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.
564 |
565 | To enable importing files without using relative paths, you can add the `--include-path` option to the command in `package.json`.
566 |
567 | ```
568 | "build-css": "node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/",
569 | "watch-css": "npm run build-css && node-sass-chokidar --include-path ./src --include-path ./node_modules src/ -o src/ --watch --recursive",
570 | ```
571 |
572 | This will allow you to do imports like
573 |
574 | ```scss
575 | @import 'styles/_colors.scss'; // assuming a styles directory under src/
576 | @import 'nprogress/nprogress'; // importing a css file from the nprogress node module
577 | ```
578 |
579 | 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.
580 |
581 | 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:
582 |
583 | ```sh
584 | npm install --save npm-run-all
585 | ```
586 |
587 | Alternatively you may use `yarn`:
588 |
589 | ```sh
590 | yarn add npm-run-all
591 | ```
592 |
593 | Then we can change `start` and `build` scripts to include the CSS preprocessor commands:
594 |
595 | ```diff
596 | "scripts": {
597 | "build-css": "node-sass-chokidar src/ -o src/",
598 | "watch-css": "npm run build-css && node-sass-chokidar src/ -o src/ --watch --recursive",
599 | - "start": "react-scripts start",
600 | - "build": "react-scripts build",
601 | + "start-js": "react-scripts start",
602 | + "start": "npm-run-all -p watch-css start-js",
603 | + "build-js": "react-scripts build",
604 | + "build": "npm-run-all build-css build-js",
605 | "test": "react-scripts test --env=jsdom",
606 | "eject": "react-scripts eject"
607 | }
608 | ```
609 |
610 | Now running `npm start` and `npm run build` also builds Sass files.
611 |
612 | **Why `node-sass-chokidar`?**
613 |
614 | `node-sass` has been reported as having the following issues:
615 |
616 | - `node-sass --watch` has been reported to have *performance issues* in certain conditions when used in a virtual machine or with docker.
617 |
618 | - Infinite styles compiling [#1939](https://github.com/facebookincubator/create-react-app/issues/1939)
619 |
620 | - `node-sass` has been reported as having issues with detecting new files in a directory [#1891](https://github.com/sass/node-sass/issues/1891)
621 |
622 | `node-sass-chokidar` is used here as it addresses these issues.
623 |
624 | ## Adding Images, Fonts, and Files
625 |
626 | With Webpack, using static assets like images and fonts works similarly to CSS.
627 |
628 | You can **`import` a file right in a JavaScript module**. This tells Webpack to include that file in the bundle. Unlike CSS imports, importing a file gives you a string value. This value is the final path you can reference in your code, e.g. as the `src` attribute of an image or the `href` of a link to a PDF.
629 |
630 | To reduce the number of requests to the server, importing images that are less than 10,000 bytes returns a [data URI](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URIs) instead of a path. This applies to the following file extensions: bmp, gif, jpg, jpeg, and png. SVG files are excluded due to [#1153](https://github.com/facebookincubator/create-react-app/issues/1153).
631 |
632 | Here is an example:
633 |
634 | ```js
635 | import React from 'react';
636 | import logo from './logo.png'; // Tell Webpack this JS file uses this image
637 |
638 | console.log(logo); // /logo.84287d09.png
639 |
640 | function Header() {
641 | // Import result is the URL of your image
642 | return ;
643 | }
644 |
645 | export default Header;
646 | ```
647 |
648 | This ensures that when the project is built, Webpack will correctly move the images into the build folder, and provide us with correct paths.
649 |
650 | This works in CSS too:
651 |
652 | ```css
653 | .Logo {
654 | background-image: url(./logo.png);
655 | }
656 | ```
657 |
658 | 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.
659 |
660 | Please be advised that this is also a custom feature of Webpack.
661 |
662 | **It is not required for React** but many people enjoy it (and React Native uses a similar mechanism for images).
663 | An alternative way of handling static assets is described in the next section.
664 |
665 | ## Using the `public` Folder
666 |
667 | >Note: this feature is available with `react-scripts@0.5.0` and higher.
668 |
669 | ### Changing the HTML
670 |
671 | The `public` folder contains the HTML file so you can tweak it, for example, to [set the page title](#changing-the-page-title).
672 | The `
1180 | ```
1181 |
1182 | 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.**
1183 |
1184 | ## Running Tests
1185 |
1186 | >Note: this feature is available with `react-scripts@0.3.0` and higher.
1187 | >[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)
1188 |
1189 | 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.
1190 |
1191 | 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.
1192 |
1193 | 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.
1194 |
1195 | 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.
1196 |
1197 | ### Filename Conventions
1198 |
1199 | Jest will look for test files with any of the following popular naming conventions:
1200 |
1201 | * Files with `.js` suffix in `__tests__` folders.
1202 | * Files with `.test.js` suffix.
1203 | * Files with `.spec.js` suffix.
1204 |
1205 | The `.test.js` / `.spec.js` files (or the `__tests__` folders) can be located at any depth under the `src` top level folder.
1206 |
1207 | 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.
1208 |
1209 | ### Command Line Interface
1210 |
1211 | 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.
1212 |
1213 | 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:
1214 |
1215 | 
1216 |
1217 | ### Version Control Integration
1218 |
1219 | 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 run 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.
1220 |
1221 | 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.
1222 |
1223 | 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.
1224 |
1225 | ### Writing Tests
1226 |
1227 | 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.
1228 |
1229 | Jest provides a built-in `expect()` global function for making assertions. A basic test could look like this:
1230 |
1231 | ```js
1232 | import sum from './sum';
1233 |
1234 | it('sums numbers', () => {
1235 | expect(sum(1, 2)).toEqual(3);
1236 | expect(sum(2, 2)).toEqual(4);
1237 | });
1238 | ```
1239 |
1240 | All `expect()` matchers supported by Jest are [extensively documented here](https://facebook.github.io/jest/docs/en/expect.html#content).
1241 | You can also use [`jest.fn()` and `expect(fn).toBeCalled()`](https://facebook.github.io/jest/docs/en/expect.html#tohavebeencalled) to create “spies” or mock functions.
1242 |
1243 | ### Testing Components
1244 |
1245 | 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.
1246 |
1247 | 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:
1248 |
1249 | ```js
1250 | import React from 'react';
1251 | import ReactDOM from 'react-dom';
1252 | import App from './App';
1253 |
1254 | it('renders without crashing', () => {
1255 | const div = document.createElement('div');
1256 | ReactDOM.render( , div);
1257 | });
1258 | ```
1259 |
1260 | 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`.
1261 |
1262 | 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.
1263 |
1264 | 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/). To install it, run:
1265 |
1266 | ```sh
1267 | npm install --save enzyme enzyme-adapter-react-16 react-test-renderer
1268 | ```
1269 |
1270 | Alternatively you may use `yarn`:
1271 |
1272 | ```sh
1273 | yarn add enzyme enzyme-adapter-react-16 react-test-renderer
1274 | ```
1275 |
1276 | As of Enzyme 3, you will need to install Enzyme along with an Adapter corresponding to the version of React you are using. (The examples above use the adapter for React 16.)
1277 |
1278 | The adapter will also need to be configured in your [global setup file](#initializing-test-environment):
1279 |
1280 | #### `src/setupTests.js`
1281 | ```js
1282 | import { configure } from 'enzyme';
1283 | import Adapter from 'enzyme-adapter-react-16';
1284 |
1285 | configure({ adapter: new Adapter() });
1286 | ```
1287 |
1288 | Now you can write a smoke test with it:
1289 |
1290 | ```js
1291 | import React from 'react';
1292 | import { shallow } from 'enzyme';
1293 | import App from './App';
1294 |
1295 | it('renders without crashing', () => {
1296 | shallow( );
1297 | });
1298 | ```
1299 |
1300 | 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.
1301 |
1302 | 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.
1303 |
1304 | Here is an example from Enzyme documentation that asserts specific output, rewritten to use Jest matchers:
1305 |
1306 | ```js
1307 | import React from 'react';
1308 | import { shallow } from 'enzyme';
1309 | import App from './App';
1310 |
1311 | it('renders welcome message', () => {
1312 | const wrapper = shallow( );
1313 | const welcome = Welcome to React ;
1314 | // expect(wrapper.contains(welcome)).to.equal(true);
1315 | expect(wrapper.contains(welcome)).toEqual(true);
1316 | });
1317 | ```
1318 |
1319 | All Jest matchers are [extensively documented here](http://facebook.github.io/jest/docs/en/expect.html).
1320 | Nevertheless you can use a third-party assertion library like [Chai](http://chaijs.com/) if you want to, as described below.
1321 |
1322 | 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.
1323 |
1324 | ```js
1325 | expect(wrapper).toContainReact(welcome)
1326 | ```
1327 |
1328 | To enable this, install `jest-enzyme`:
1329 |
1330 | ```sh
1331 | npm install --save jest-enzyme
1332 | ```
1333 |
1334 | Alternatively you may use `yarn`:
1335 |
1336 | ```sh
1337 | yarn add jest-enzyme
1338 | ```
1339 |
1340 | Import it in [`src/setupTests.js`](#initializing-test-environment) to make its matchers available in every test:
1341 |
1342 | ```js
1343 | import 'jest-enzyme';
1344 | ```
1345 |
1346 | ### Using Third Party Assertion Libraries
1347 |
1348 | 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).
1349 |
1350 | 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:
1351 |
1352 | ```js
1353 | import sinon from 'sinon';
1354 | import { expect } from 'chai';
1355 | ```
1356 |
1357 | and then use them in your tests like you normally do.
1358 |
1359 | ### Initializing Test Environment
1360 |
1361 | >Note: this feature is available with `react-scripts@0.4.0` and higher.
1362 |
1363 | 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.
1364 |
1365 | For example:
1366 |
1367 | #### `src/setupTests.js`
1368 | ```js
1369 | const localStorageMock = {
1370 | getItem: jest.fn(),
1371 | setItem: jest.fn(),
1372 | clear: jest.fn()
1373 | };
1374 | global.localStorage = localStorageMock
1375 | ```
1376 |
1377 | ### Focusing and Excluding Tests
1378 |
1379 | You can replace `it()` with `xit()` to temporarily exclude a test from being executed.
1380 | Similarly, `fit()` lets you focus on a specific test without running any other tests.
1381 |
1382 | ### Coverage Reporting
1383 |
1384 | Jest has an integrated coverage reporter that works well with ES6 and requires no configuration.
1385 | Run `npm test -- --coverage` (note extra `--` in the middle) to include a coverage report like this:
1386 |
1387 | 
1388 |
1389 | Note that tests run much slower with coverage so it is recommended to run it separately from your normal workflow.
1390 |
1391 | #### Configuration
1392 |
1393 | The default Jest coverage configuration can be overriden by adding any of the following supported keys to a Jest config in your package.json.
1394 |
1395 | Supported overrides:
1396 | - [`collectCoverageFrom`](https://facebook.github.io/jest/docs/en/configuration.html#collectcoveragefrom-array)
1397 | - [`coverageReporters`](https://facebook.github.io/jest/docs/en/configuration.html#coveragereporters-array-string)
1398 | - [`coverageThreshold`](https://facebook.github.io/jest/docs/en/configuration.html#coveragethreshold-object)
1399 | - [`snapshotSerializers`](https://facebook.github.io/jest/docs/en/configuration.html#snapshotserializers-array-string)
1400 |
1401 | Example package.json:
1402 |
1403 | ```json
1404 | {
1405 | "name": "your-package",
1406 | "jest": {
1407 | "collectCoverageFrom" : [
1408 | "src/**/*.{js,jsx}",
1409 | "!/node_modules/",
1410 | "!/path/to/dir/"
1411 | ],
1412 | "coverageThreshold": {
1413 | "global": {
1414 | "branches": 90,
1415 | "functions": 90,
1416 | "lines": 90,
1417 | "statements": 90
1418 | }
1419 | },
1420 | "coverageReporters": ["text"],
1421 | "snapshotSerializers": ["my-serializer-module"]
1422 | }
1423 | }
1424 | ```
1425 |
1426 | ### Continuous Integration
1427 |
1428 | 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`.
1429 |
1430 | 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.
1431 |
1432 | Popular CI servers already set the environment variable `CI` by default but you can do this yourself too:
1433 |
1434 | ### On CI servers
1435 | #### Travis CI
1436 |
1437 | 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.
1438 | 1. Add a `.travis.yml` file to your git repository.
1439 | ```
1440 | language: node_js
1441 | node_js:
1442 | - 6
1443 | cache:
1444 | directories:
1445 | - node_modules
1446 | script:
1447 | - npm run build
1448 | - npm test
1449 | ```
1450 | 1. Trigger your first build with a git push.
1451 | 1. [Customize your Travis CI Build](https://docs.travis-ci.com/user/customizing-the-build/) if needed.
1452 |
1453 | #### CircleCI
1454 |
1455 | Follow [this article](https://medium.com/@knowbody/circleci-and-zeits-now-sh-c9b7eebcd3c1) to set up CircleCI with a Create React App project.
1456 |
1457 | ### On your own environment
1458 | ##### Windows (cmd.exe)
1459 |
1460 | ```cmd
1461 | set CI=true&&npm test
1462 | ```
1463 |
1464 | ```cmd
1465 | set CI=true&&npm run build
1466 | ```
1467 |
1468 | (Note: the lack of whitespace is intentional.)
1469 |
1470 | ##### Linux, macOS (Bash)
1471 |
1472 | ```bash
1473 | CI=true npm test
1474 | ```
1475 |
1476 | ```bash
1477 | CI=true npm run build
1478 | ```
1479 |
1480 | The test command will force Jest to run tests once instead of launching the watcher.
1481 |
1482 | > 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.
1483 |
1484 | The build command will check for linter warnings and fail if any are found.
1485 |
1486 | ### Disabling jsdom
1487 |
1488 | By default, the `package.json` of the generated project looks like this:
1489 |
1490 | ```js
1491 | "scripts": {
1492 | "start": "react-scripts start",
1493 | "build": "react-scripts build",
1494 | "test": "react-scripts test --env=jsdom"
1495 | ```
1496 |
1497 | 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:
1498 |
1499 | ```diff
1500 | "scripts": {
1501 | "start": "react-scripts start",
1502 | "build": "react-scripts build",
1503 | - "test": "react-scripts test --env=jsdom"
1504 | + "test": "react-scripts test"
1505 | ```
1506 |
1507 | To help you make up your mind, here is a list of APIs that **need jsdom**:
1508 |
1509 | * Any browser globals like `window` and `document`
1510 | * [`ReactDOM.render()`](https://facebook.github.io/react/docs/top-level-api.html#reactdom.render)
1511 | * [`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)
1512 | * [`mount()`](http://airbnb.io/enzyme/docs/api/mount.html) in [Enzyme](http://airbnb.io/enzyme/index.html)
1513 |
1514 | In contrast, **jsdom is not needed** for the following APIs:
1515 |
1516 | * [`TestUtils.createRenderer()`](https://facebook.github.io/react/docs/test-utils.html#shallow-rendering) (shallow rendering)
1517 | * [`shallow()`](http://airbnb.io/enzyme/docs/api/shallow.html) in [Enzyme](http://airbnb.io/enzyme/index.html)
1518 |
1519 | Finally, jsdom is also not needed for [snapshot testing](http://facebook.github.io/jest/blog/2016/07/27/jest-14.html).
1520 |
1521 | ### Snapshot Testing
1522 |
1523 | 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)
1524 |
1525 | ### Editor Integration
1526 |
1527 | 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.
1528 |
1529 | 
1530 |
1531 | ## Developing Components in Isolation
1532 |
1533 | Usually, in an app, you have a lot of UI components, and each of them has many different states.
1534 | For an example, a simple button component could have following states:
1535 |
1536 | * In a regular state, with a text label.
1537 | * In the disabled mode.
1538 | * In a loading state.
1539 |
1540 | Usually, it’s hard to see these states without running a sample app or some examples.
1541 |
1542 | Create React App doesn’t include any tools for this by default, but you can easily add [Storybook for React](https://storybook.js.org) ([source](https://github.com/storybooks/storybook)) or [React Styleguidist](https://react-styleguidist.js.org/) ([source](https://github.com/styleguidist/react-styleguidist)) to your project. **These are third-party tools that let you develop components and see all their states in isolation from your app**.
1543 |
1544 | 
1545 |
1546 | You can also deploy your Storybook or style guide 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.
1547 |
1548 | ### Getting Started with Storybook
1549 |
1550 | Storybook is a development environment for React UI components. It allows you to browse a component library, view the different states of each component, and interactively develop and test components.
1551 |
1552 | First, install the following npm package globally:
1553 |
1554 | ```sh
1555 | npm install -g @storybook/cli
1556 | ```
1557 |
1558 | Then, run the following command inside your app’s directory:
1559 |
1560 | ```sh
1561 | getstorybook
1562 | ```
1563 |
1564 | After that, follow the instructions on the screen.
1565 |
1566 | Learn more about React Storybook:
1567 |
1568 | * Screencast: [Getting Started with React Storybook](https://egghead.io/lessons/react-getting-started-with-react-storybook)
1569 | * [GitHub Repo](https://github.com/storybooks/storybook)
1570 | * [Documentation](https://storybook.js.org/basics/introduction/)
1571 | * [Snapshot Testing UI](https://github.com/storybooks/storybook/tree/master/addons/storyshots) with Storybook + addon/storyshot
1572 |
1573 | ### Getting Started with Styleguidist
1574 |
1575 | Styleguidist combines a style guide, where all your components are presented on a single page with their props documentation and usage examples, with an environment for developing components in isolation, similar to Storybook. In Styleguidist you write examples in Markdown, where each code snippet is rendered as a live editable playground.
1576 |
1577 | First, install Styleguidist:
1578 |
1579 | ```sh
1580 | npm install --save react-styleguidist
1581 | ```
1582 |
1583 | Alternatively you may use `yarn`:
1584 |
1585 | ```sh
1586 | yarn add react-styleguidist
1587 | ```
1588 |
1589 | Then, add these scripts to your `package.json`:
1590 |
1591 | ```diff
1592 | "scripts": {
1593 | + "styleguide": "styleguidist server",
1594 | + "styleguide:build": "styleguidist build",
1595 | "start": "react-scripts start",
1596 | ```
1597 |
1598 | Then, run the following command inside your app’s directory:
1599 |
1600 | ```sh
1601 | npm run styleguide
1602 | ```
1603 |
1604 | After that, follow the instructions on the screen.
1605 |
1606 | Learn more about React Styleguidist:
1607 |
1608 | * [GitHub Repo](https://github.com/styleguidist/react-styleguidist)
1609 | * [Documentation](https://react-styleguidist.js.org/docs/getting-started.html)
1610 |
1611 | ## Making a Progressive Web App
1612 |
1613 | By default, the production build is a fully functional, offline-first
1614 | [Progressive Web App](https://developers.google.com/web/progressive-web-apps/).
1615 |
1616 | Progressive Web Apps are faster and more reliable than traditional web pages, and provide an engaging mobile experience:
1617 |
1618 | * All static site assets are cached so that your page loads fast on subsequent visits, regardless of network connectivity (such as 2G or 3G). Updates are downloaded in the background.
1619 | * Your app will work regardless of network state, even if offline. This means your users will be able to use your app at 10,000 feet and on the subway.
1620 | * On mobile devices, your app can be added directly to the user's home screen, app icon and all. You can also re-engage users using web **push notifications**. This eliminates the need for the app store.
1621 |
1622 | The [`sw-precache-webpack-plugin`](https://github.com/goldhand/sw-precache-webpack-plugin)
1623 | is integrated into production configuration,
1624 | and it will take care of generating a service worker file that will automatically
1625 | precache all of your local assets and keep them up to date as you deploy updates.
1626 | The service worker will use a [cache-first strategy](https://developers.google.com/web/fundamentals/instant-and-offline/offline-cookbook/#cache-falling-back-to-network)
1627 | for handling all requests for local assets, including the initial HTML, ensuring
1628 | that your web app is reliably fast, even on a slow or unreliable network.
1629 |
1630 | ### Opting Out of Caching
1631 |
1632 | If you would prefer not to enable service workers prior to your initial
1633 | production deployment, then remove the call to `registerServiceWorker()`
1634 | from [`src/index.js`](src/index.js).
1635 |
1636 | If you had previously enabled service workers in your production deployment and
1637 | have decided that you would like to disable them for all your existing users,
1638 | you can swap out the call to `registerServiceWorker()` in
1639 | [`src/index.js`](src/index.js) first by modifying the service worker import:
1640 | ```javascript
1641 | import { unregister } from './registerServiceWorker';
1642 | ```
1643 | and then call `unregister()` instead.
1644 | After the user visits a page that has `unregister()`,
1645 | the service worker will be uninstalled. Note that depending on how `/service-worker.js` is served,
1646 | it may take up to 24 hours for the cache to be invalidated.
1647 |
1648 | ### Offline-First Considerations
1649 |
1650 | 1. Service workers [require HTTPS](https://developers.google.com/web/fundamentals/getting-started/primers/service-workers#you_need_https),
1651 | although to facilitate local testing, that policy
1652 | [does not apply to `localhost`](http://stackoverflow.com/questions/34160509/options-for-testing-service-workers-via-http/34161385#34161385).
1653 | If your production web server does not support HTTPS, then the service worker
1654 | registration will fail, but the rest of your web app will remain functional.
1655 |
1656 | 1. Service workers are [not currently supported](https://jakearchibald.github.io/isserviceworkerready/)
1657 | in all web browsers. Service worker registration [won't be attempted](src/registerServiceWorker.js)
1658 | on browsers that lack support.
1659 |
1660 | 1. The service worker is only enabled in the [production environment](#deployment),
1661 | e.g. the output of `npm run build`. It's recommended that you do not enable an
1662 | offline-first service worker in a development environment, as it can lead to
1663 | frustration when previously cached assets are used and do not include the latest
1664 | changes you've made locally.
1665 |
1666 | 1. If you *need* to test your offline-first service worker locally, build
1667 | the application (using `npm run build`) and run a simple http server from your
1668 | build directory. After running the build script, `create-react-app` will give
1669 | instructions for one way to test your production build locally and the [deployment instructions](#deployment) have
1670 | instructions for using other methods. *Be sure to always use an
1671 | incognito window to avoid complications with your browser cache.*
1672 |
1673 | 1. If possible, configure your production environment to serve the generated
1674 | `service-worker.js` [with HTTP caching disabled](http://stackoverflow.com/questions/38843970/service-worker-javascript-update-frequency-every-24-hours).
1675 | If that's not possible—[GitHub Pages](#github-pages), for instance, does not
1676 | allow you to change the default 10 minute HTTP cache lifetime—then be aware
1677 | that if you visit your production site, and then revisit again before
1678 | `service-worker.js` has expired from your HTTP cache, you'll continue to get
1679 | the previously cached assets from the service worker. If you have an immediate
1680 | need to view your updated production deployment, performing a shift-refresh
1681 | will temporarily disable the service worker and retrieve all assets from the
1682 | network.
1683 |
1684 | 1. Users aren't always familiar with offline-first web apps. It can be useful to
1685 | [let the user know](https://developers.google.com/web/fundamentals/instant-and-offline/offline-ux#inform_the_user_when_the_app_is_ready_for_offline_consumption)
1686 | when the service worker has finished populating your caches (showing a "This web
1687 | app works offline!" message) and also let them know when the service worker has
1688 | fetched the latest updates that will be available the next time they load the
1689 | page (showing a "New content is available; please refresh." message). Showing
1690 | this messages is currently left as an exercise to the developer, but as a
1691 | starting point, you can make use of the logic included in [`src/registerServiceWorker.js`](src/registerServiceWorker.js), which
1692 | demonstrates which service worker lifecycle events to listen for to detect each
1693 | scenario, and which as a default, just logs appropriate messages to the
1694 | JavaScript console.
1695 |
1696 | 1. By default, the generated service worker file will not intercept or cache any
1697 | cross-origin traffic, like HTTP [API requests](#integrating-with-an-api-backend),
1698 | images, or embeds loaded from a different domain. If you would like to use a
1699 | runtime caching strategy for those requests, you can [`eject`](#npm-run-eject)
1700 | and then configure the
1701 | [`runtimeCaching`](https://github.com/GoogleChrome/sw-precache#runtimecaching-arrayobject)
1702 | option in the `SWPrecacheWebpackPlugin` section of
1703 | [`webpack.config.prod.js`](../config/webpack.config.prod.js).
1704 |
1705 | ### Progressive Web App Metadata
1706 |
1707 | The default configuration includes a web app manifest located at
1708 | [`public/manifest.json`](public/manifest.json), that you can customize with
1709 | details specific to your web application.
1710 |
1711 | When a user adds a web app to their homescreen using Chrome or Firefox on
1712 | Android, the metadata in [`manifest.json`](public/manifest.json) determines what
1713 | icons, names, and branding colors to use when the web app is displayed.
1714 | [The Web App Manifest guide](https://developers.google.com/web/fundamentals/engage-and-retain/web-app-manifest/)
1715 | provides more context about what each field means, and how your customizations
1716 | will affect your users' experience.
1717 |
1718 | ## Analyzing the Bundle Size
1719 |
1720 | [Source map explorer](https://www.npmjs.com/package/source-map-explorer) analyzes
1721 | JavaScript bundles using the source maps. This helps you understand where code
1722 | bloat is coming from.
1723 |
1724 | To add Source map explorer to a Create React App project, follow these steps:
1725 |
1726 | ```sh
1727 | npm install --save source-map-explorer
1728 | ```
1729 |
1730 | Alternatively you may use `yarn`:
1731 |
1732 | ```sh
1733 | yarn add source-map-explorer
1734 | ```
1735 |
1736 | Then in `package.json`, add the following line to `scripts`:
1737 |
1738 | ```diff
1739 | "scripts": {
1740 | + "analyze": "source-map-explorer build/static/js/main.*",
1741 | "start": "react-scripts start",
1742 | "build": "react-scripts build",
1743 | "test": "react-scripts test --env=jsdom",
1744 | ```
1745 |
1746 | Then to analyze the bundle run the production build then run the analyze
1747 | script.
1748 |
1749 | ```
1750 | npm run build
1751 | npm run analyze
1752 | ```
1753 |
1754 | ## Deployment
1755 |
1756 | `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.
1757 |
1758 | ### Static Server
1759 |
1760 | For environments using [Node](https://nodejs.org/), the easiest way to handle this would be to install [serve](https://github.com/zeit/serve) and let it handle the rest:
1761 |
1762 | ```sh
1763 | npm install -g serve
1764 | serve -s build
1765 | ```
1766 |
1767 | The last command shown above will serve your static site on the port **5000**. Like many of [serve](https://github.com/zeit/serve)’s internal settings, the port can be adjusted using the `-p` or `--port` flags.
1768 |
1769 | Run this command to get a full list of the options available:
1770 |
1771 | ```sh
1772 | serve -h
1773 | ```
1774 |
1775 | ### Other Solutions
1776 |
1777 | You don’t necessarily need a static server in order to run a Create React App project in production. It works just as fine integrated into an existing dynamic one.
1778 |
1779 | Here’s a programmatic example using [Node](https://nodejs.org/) and [Express](http://expressjs.com/):
1780 |
1781 | ```javascript
1782 | const express = require('express');
1783 | const path = require('path');
1784 | const app = express();
1785 |
1786 | app.use(express.static(path.join(__dirname, 'build')));
1787 |
1788 | app.get('/', function (req, res) {
1789 | res.sendFile(path.join(__dirname, 'build', 'index.html'));
1790 | });
1791 |
1792 | app.listen(9000);
1793 | ```
1794 |
1795 | The choice of your server software isn’t important either. Since Create React App is completely platform-agnostic, there’s no need to explicitly use Node.
1796 |
1797 | The `build` folder with static assets is the only output produced by Create React App.
1798 |
1799 | 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.
1800 |
1801 | ### Serving Apps with Client-Side Routing
1802 |
1803 | 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.
1804 |
1805 | 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:
1806 |
1807 | ```diff
1808 | app.use(express.static(path.join(__dirname, 'build')));
1809 |
1810 | -app.get('/', function (req, res) {
1811 | +app.get('/*', function (req, res) {
1812 | res.sendFile(path.join(__dirname, 'build', 'index.html'));
1813 | });
1814 | ```
1815 |
1816 | If you’re using [Apache HTTP Server](https://httpd.apache.org/), you need to create a `.htaccess` file in the `public` folder that looks like this:
1817 |
1818 | ```
1819 | Options -MultiViews
1820 | RewriteEngine On
1821 | RewriteCond %{REQUEST_FILENAME} !-f
1822 | RewriteRule ^ index.html [QSA,L]
1823 | ```
1824 |
1825 | It will get copied to the `build` folder when you run `npm run build`.
1826 |
1827 | If you’re using [Apache Tomcat](http://tomcat.apache.org/), you need to follow [this Stack Overflow answer](https://stackoverflow.com/a/41249464/4878474).
1828 |
1829 | Now requests to `/todos/42` will be handled correctly both in development and in production.
1830 |
1831 | On a production build, and in a browser that supports [service workers](https://developers.google.com/web/fundamentals/getting-started/primers/service-workers),
1832 | the service worker will automatically handle all navigation requests, like for
1833 | `/todos/42`, by serving the cached copy of your `index.html`. This
1834 | service worker navigation routing can be configured or disabled by
1835 | [`eject`ing](#npm-run-eject) and then modifying the
1836 | [`navigateFallback`](https://github.com/GoogleChrome/sw-precache#navigatefallback-string)
1837 | and [`navigateFallbackWhitelist`](https://github.com/GoogleChrome/sw-precache#navigatefallbackwhitelist-arrayregexp)
1838 | options of the `SWPreachePlugin` [configuration](../config/webpack.config.prod.js).
1839 |
1840 | When users install your app to the homescreen of their device the default configuration will make a shortcut to `/index.html`. This may not work for client-side routers which expect the app to be served from `/`. Edit the web app manifest at [`public/manifest.json`](public/manifest.json) and change `start_url` to match the required URL scheme, for example:
1841 |
1842 | ```js
1843 | "start_url": ".",
1844 | ```
1845 |
1846 | ### Building for Relative Paths
1847 |
1848 | By default, Create React App produces a build assuming your app is hosted at the server root.
1849 | To override this, specify the `homepage` in your `package.json`, for example:
1850 |
1851 | ```js
1852 | "homepage": "http://mywebsite.com/relativepath",
1853 | ```
1854 |
1855 | This will let Create React App correctly infer the root path to use in the generated HTML file.
1856 |
1857 | **Note**: If you are using `react-router@^4`, you can root ` `s using the `basename` prop on any ``.
1858 | More information [here](https://reacttraining.com/react-router/web/api/BrowserRouter/basename-string).
1859 |
1860 | For example:
1861 | ```js
1862 |
1863 | // renders
1864 | ```
1865 |
1866 | #### Serving the Same Build from Different Paths
1867 |
1868 | >Note: this feature is available with `react-scripts@0.9.0` and higher.
1869 |
1870 | 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`:
1871 |
1872 | ```js
1873 | "homepage": ".",
1874 | ```
1875 |
1876 | 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.
1877 |
1878 | ### [Azure](https://azure.microsoft.com/)
1879 |
1880 | 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.
1881 |
1882 | ### [Firebase](https://firebase.google.com/)
1883 |
1884 | 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.
1885 |
1886 | 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`.
1887 |
1888 | ```sh
1889 | === Project Setup
1890 |
1891 | First, let's associate this project directory with a Firebase project.
1892 | You can create multiple project aliases by running firebase use --add,
1893 | but for now we'll just set up a default project.
1894 |
1895 | ? What Firebase project do you want to associate as default? Example app (example-app-fd690)
1896 |
1897 | === Database Setup
1898 |
1899 | Firebase Realtime Database Rules allow you to define how your data should be
1900 | structured and when your data can be read from and written to.
1901 |
1902 | ? What file should be used for Database Rules? database.rules.json
1903 | ✔ Database Rules for example-app-fd690 have been downloaded to database.rules.json.
1904 | Future modifications to database.rules.json will update Database Rules when you run
1905 | firebase deploy.
1906 |
1907 | === Hosting Setup
1908 |
1909 | Your public directory is the folder (relative to your project directory) that
1910 | will contain Hosting assets to uploaded with firebase deploy. If you
1911 | have a build process for your assets, use your build's output directory.
1912 |
1913 | ? What do you want to use as your public directory? build
1914 | ? Configure as a single-page app (rewrite all urls to /index.html)? Yes
1915 | ✔ Wrote build/index.html
1916 |
1917 | i Writing configuration info to firebase.json...
1918 | i Writing project information to .firebaserc...
1919 |
1920 | ✔ Firebase initialization complete!
1921 | ```
1922 |
1923 | Now, after you create a production build with `npm run build`, you can deploy it by running `firebase deploy`.
1924 |
1925 | ```sh
1926 | === Deploying to 'example-app-fd690'...
1927 |
1928 | i deploying database, hosting
1929 | ✔ database: rules ready to deploy.
1930 | i hosting: preparing build directory for upload...
1931 | Uploading: [============================== ] 75%✔ hosting: build folder uploaded successfully
1932 | ✔ hosting: 8 files uploaded successfully
1933 | i starting release process (may take several minutes)...
1934 |
1935 | ✔ Deploy complete!
1936 |
1937 | Project Console: https://console.firebase.google.com/project/example-app-fd690/overview
1938 | Hosting URL: https://example-app-fd690.firebaseapp.com
1939 | ```
1940 |
1941 | For more information see [Add Firebase to your JavaScript Project](https://firebase.google.com/docs/web/setup).
1942 |
1943 | ### [GitHub Pages](https://pages.github.com/)
1944 |
1945 | >Note: this feature is available with `react-scripts@0.2.0` and higher.
1946 |
1947 | #### Step 1: Add `homepage` to `package.json`
1948 |
1949 | **The step below is important!**
1950 | **If you skip it, your app will not deploy correctly.**
1951 |
1952 | Open your `package.json` and add a `homepage` field:
1953 |
1954 | ```js
1955 | "homepage": "https://myusername.github.io/my-app",
1956 | ```
1957 |
1958 | Create React App uses the `homepage` field to determine the root URL in the built HTML file.
1959 |
1960 | #### Step 2: Install `gh-pages` and add `deploy` to `scripts` in `package.json`
1961 |
1962 | Now, whenever you run `npm run build`, you will see a cheat sheet with instructions on how to deploy to GitHub Pages.
1963 |
1964 | To publish it at [https://myusername.github.io/my-app](https://myusername.github.io/my-app), run:
1965 |
1966 | ```sh
1967 | npm install --save gh-pages
1968 | ```
1969 |
1970 | Alternatively you may use `yarn`:
1971 |
1972 | ```sh
1973 | yarn add gh-pages
1974 | ```
1975 |
1976 | Add the following scripts in your `package.json`:
1977 |
1978 | ```diff
1979 | "scripts": {
1980 | + "predeploy": "npm run build",
1981 | + "deploy": "gh-pages -d build",
1982 | "start": "react-scripts start",
1983 | "build": "react-scripts build",
1984 | ```
1985 |
1986 | The `predeploy` script will run automatically before `deploy` is run.
1987 |
1988 | #### Step 3: Deploy the site by running `npm run deploy`
1989 |
1990 | Then run:
1991 |
1992 | ```sh
1993 | npm run deploy
1994 | ```
1995 |
1996 | #### Step 4: Ensure your project’s settings use `gh-pages`
1997 |
1998 | Finally, make sure **GitHub Pages** option in your GitHub project settings is set to use the `gh-pages` branch:
1999 |
2000 |
2001 |
2002 | #### Step 5: Optionally, configure the domain
2003 |
2004 | You can configure a custom domain with GitHub Pages by adding a `CNAME` file to the `public/` folder.
2005 |
2006 | #### Notes on client-side routing
2007 |
2008 | 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:
2009 |
2010 | * 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://reacttraining.com/react-router/web/api/Router) about different history implementations in React Router.
2011 | * 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).
2012 |
2013 | ### [Heroku](https://www.heroku.com/)
2014 |
2015 | Use the [Heroku Buildpack for Create React App](https://github.com/mars/create-react-app-buildpack).
2016 | You can find instructions in [Deploying React with Zero Configuration](https://blog.heroku.com/deploying-react-with-zero-configuration).
2017 |
2018 | #### Resolving Heroku Deployment Errors
2019 |
2020 | Sometimes `npm run build` works locally but fails during deploy via Heroku. Following are the most common cases.
2021 |
2022 | ##### "Module not found: Error: Cannot resolve 'file' or 'directory'"
2023 |
2024 | If you get something like this:
2025 |
2026 | ```
2027 | remote: Failed to create a production build. Reason:
2028 | remote: Module not found: Error: Cannot resolve 'file' or 'directory'
2029 | MyDirectory in /tmp/build_1234/src
2030 | ```
2031 |
2032 | 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.
2033 |
2034 | 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.
2035 |
2036 | ##### "Could not find a required file."
2037 |
2038 | If you exclude or ignore necessary files from the package you will see a error similar this one:
2039 |
2040 | ```
2041 | remote: Could not find a required file.
2042 | remote: Name: `index.html`
2043 | remote: Searched in: /tmp/build_a2875fc163b209225122d68916f1d4df/public
2044 | remote:
2045 | remote: npm ERR! Linux 3.13.0-105-generic
2046 | remote: npm ERR! argv "/tmp/build_a2875fc163b209225122d68916f1d4df/.heroku/node/bin/node" "/tmp/build_a2875fc163b209225122d68916f1d4df/.heroku/node/bin/npm" "run" "build"
2047 | ```
2048 |
2049 | 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`.
2050 |
2051 | ### [Netlify](https://www.netlify.com/)
2052 |
2053 | **To do a manual deploy to Netlify’s CDN:**
2054 |
2055 | ```sh
2056 | npm install netlify-cli
2057 | netlify deploy
2058 | ```
2059 |
2060 | Choose `build` as the path to deploy.
2061 |
2062 | **To setup continuous delivery:**
2063 |
2064 | With this setup Netlify will build and deploy when you push to git or open a pull request:
2065 |
2066 | 1. [Start a new netlify project](https://app.netlify.com/signup)
2067 | 2. Pick your Git hosting service and select your repository
2068 | 3. Click `Build your site`
2069 |
2070 | **Support for client-side routing:**
2071 |
2072 | To support `pushState`, make sure to create a `public/_redirects` file with the following rewrite rules:
2073 |
2074 | ```
2075 | /* /index.html 200
2076 | ```
2077 |
2078 | When you build the project, Create React App will place the `public` folder contents into the build output.
2079 |
2080 | ### [Now](https://zeit.co/now)
2081 |
2082 | Now offers a zero-configuration single-command deployment. You can use `now` to deploy your app for free.
2083 |
2084 | 1. Install the `now` command-line tool either via the recommended [desktop tool](https://zeit.co/download) or via node with `npm install -g now`.
2085 |
2086 | 2. Build your app by running `npm run build`.
2087 |
2088 | 3. Move into the build directory by running `cd build`.
2089 |
2090 | 4. Run `now --name your-project-name` from within the build directory. You will see a **now.sh** URL in your output like this:
2091 |
2092 | ```
2093 | > Ready! https://your-project-name-tpspyhtdtk.now.sh (copied to clipboard)
2094 | ```
2095 |
2096 | Paste that URL into your browser when the build is complete, and you will see your deployed app.
2097 |
2098 | Details are available in [this article.](https://zeit.co/blog/unlimited-static)
2099 |
2100 | ### [S3](https://aws.amazon.com/s3) and [CloudFront](https://aws.amazon.com/cloudfront/)
2101 |
2102 | 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 and CloudFront.
2103 |
2104 | ### [Surge](https://surge.sh/)
2105 |
2106 | 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.
2107 |
2108 | When asked about the project path, make sure to specify the `build` folder, for example:
2109 |
2110 | ```sh
2111 | project path: /path/to/project/build
2112 | ```
2113 |
2114 | 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).
2115 |
2116 | ## Advanced Configuration
2117 |
2118 | You can adjust various development and production settings by setting environment variables in your shell or with [.env](#adding-development-environment-variables-in-env).
2119 |
2120 | Variable | Development | Production | Usage
2121 | :--- | :---: | :---: | :---
2122 | 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. If you need to customize the way the browser is launched, you can specify a node script instead. Any arguments passed to `npm start` will also be passed to this script, and the url where your app is served will be the last argument. Your script's file name must have the `.js` extension.
2123 | HOST | :white_check_mark: | :x: | By default, the development web server binds to `localhost`. You may use this variable to specify a different host.
2124 | 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.
2125 | HTTPS | :white_check_mark: | :x: | When set to `true`, Create React App will run the development server in `https` mode.
2126 | 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.
2127 | 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.
2128 | REACT_EDITOR | :white_check_mark: | :x: | When an app crashes in development, you will see an error overlay with clickable stack trace. When you click on it, Create React App will try to determine the editor you are using based on currently running processes, and open the relevant source file. You can [send a pull request to detect your editor of choice](https://github.com/facebookincubator/create-react-app/issues/2636). Setting this environment variable overrides the automatic detection. If you do it, make sure your systems [PATH](https://en.wikipedia.org/wiki/PATH_(variable)) environment variable points to your editor’s bin folder.
2129 | CHOKIDAR_USEPOLLING | :white_check_mark: | :x: | When set to `true`, the watcher runs in polling mode, as necessary inside a VM. Use this option if `npm start` isn't detecting changes.
2130 | GENERATE_SOURCEMAP | :x: | :white_check_mark: | When set to `false`, source maps are not generated for a production build. This solves OOM issues on some smaller machines.
2131 |
2132 | ## Troubleshooting
2133 |
2134 | ### `npm start` doesn’t detect changes
2135 |
2136 | When you save a file while `npm start` is running, the browser should refresh with the updated code.
2137 | If this doesn’t happen, try one of the following workarounds:
2138 |
2139 | * If your project is in a Dropbox folder, try moving it out.
2140 | * 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.
2141 | * 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 [“Adjusting Your Text Editor”](https://webpack.js.org/guides/development/#adjusting-your-text-editor).
2142 | * 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).
2143 | * 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.
2144 | * If the project runs inside a virtual machine such as (a Vagrant provisioned) VirtualBox, create an `.env` file in your project directory if it doesn’t exist, and add `CHOKIDAR_USEPOLLING=true` to it. This ensures that the next time you run `npm start`, the watcher uses the polling mode, as necessary inside a VM.
2145 |
2146 | If none of these solutions help please leave a comment [in this thread](https://github.com/facebookincubator/create-react-app/issues/659).
2147 |
2148 | ### `npm test` hangs on macOS Sierra
2149 |
2150 | 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).
2151 |
2152 | 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:
2153 |
2154 | * [facebook/jest#1767](https://github.com/facebook/jest/issues/1767)
2155 | * [facebook/watchman#358](https://github.com/facebook/watchman/issues/358)
2156 | * [ember-cli/ember-cli#6259](https://github.com/ember-cli/ember-cli/issues/6259)
2157 |
2158 | 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:
2159 |
2160 | ```
2161 | watchman shutdown-server
2162 | brew update
2163 | brew reinstall watchman
2164 | ```
2165 |
2166 | You can find [other installation methods](https://facebook.github.io/watchman/docs/install.html#build-install) on the Watchman documentation page.
2167 |
2168 | If this still doesn’t help, try running `launchctl unload -F ~/Library/LaunchAgents/com.github.facebook.watchman.plist`.
2169 |
2170 | There are also reports that *uninstalling* Watchman fixes the issue. So if nothing else helps, remove it from your system and try again.
2171 |
2172 | ### `npm run build` exits too early
2173 |
2174 | It is reported that `npm run build` can fail on machines with limited memory and no swap space, which is common in cloud environments. Even with small projects this command can increase RAM usage in your system by hundreds of megabytes, so if you have less than 1 GB of available memory your build is likely to fail with the following message:
2175 |
2176 | > The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
2177 |
2178 | If you are completely sure that you didn't terminate the process, consider [adding some swap space](https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04) to the machine you’re building on, or build the project locally.
2179 |
2180 | ### `npm run build` fails on Heroku
2181 |
2182 | This may be a problem with case sensitive filenames.
2183 | Please refer to [this section](#resolving-heroku-deployment-errors).
2184 |
2185 | ### Moment.js locales are missing
2186 |
2187 | If you use a [Moment.js](https://momentjs.com/), you might notice that only the English locale is available by default. This is because the locale files are large, and you probably only need a subset of [all the locales provided by Moment.js](https://momentjs.com/#multiple-locale-support).
2188 |
2189 | To add a specific Moment.js locale to your bundle, you need to import it explicitly.
2190 | For example:
2191 |
2192 | ```js
2193 | import moment from 'moment';
2194 | import 'moment/locale/fr';
2195 | ```
2196 |
2197 | If import multiple locales this way, you can later switch between them by calling `moment.locale()` with the locale name:
2198 |
2199 | ```js
2200 | import moment from 'moment';
2201 | import 'moment/locale/fr';
2202 | import 'moment/locale/es';
2203 |
2204 | // ...
2205 |
2206 | moment.locale('fr');
2207 | ```
2208 |
2209 | This will only work for locales that have been explicitly imported before.
2210 |
2211 | ### `npm run build` fails to minify
2212 |
2213 | Some third-party packages don't compile their code to ES5 before publishing to npm. This often causes problems in the ecosystem because neither browsers (except for most modern versions) nor some tools currently support all ES6 features. We recommend to publish code on npm as ES5 at least for a few more years.
2214 |
2215 |
2216 | To resolve this:
2217 |
2218 | 1. Open an issue on the dependency's issue tracker and ask that the package be published pre-compiled.
2219 | * Note: Create React App can consume both CommonJS and ES modules. For Node.js compatibility, it is recommended that the main entry point is CommonJS. However, they can optionally provide an ES module entry point with the `module` field in `package.json`. Note that **even if a library provides an ES Modules version, it should still precompile other ES6 features to ES5 if it intends to support older browsers**.
2220 |
2221 | 2. Fork the package and publish a corrected version yourself.
2222 |
2223 | 3. If the dependency is small enough, copy it to your `src/` folder and treat it as application code.
2224 |
2225 | In the future, we might start automatically compiling incompatible third-party modules, but it is not currently supported. This approach would also slow down the production builds.
2226 |
2227 | ## Something Missing?
2228 |
2229 | 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)
2230 |
--------------------------------------------------------------------------------