├── .gitattributes ├── .gitignore ├── AspNetCoreSignalR_React.Client ├── .gitignore ├── README.md ├── package-lock.json ├── package.json ├── public │ ├── favicon.ico │ ├── index.html │ └── manifest.json ├── src │ ├── App.css │ ├── App.js │ ├── App.test.js │ ├── Chat.js │ ├── index.css │ ├── index.js │ ├── logo.svg │ └── registerServiceWorker.js └── yarn.lock ├── AspNetCoreSignalR_React.Server ├── AspNetCoreSignalR_React.Server.csproj ├── ChatHub.cs ├── Program.cs ├── Properties │ └── launchSettings.json └── Startup.cs └── AspNetCoreSignalR_React.sln /.gitattributes: -------------------------------------------------------------------------------- 1 | ############################################################################### 2 | # Set default behavior to automatically normalize line endings. 3 | ############################################################################### 4 | * text=auto 5 | 6 | ############################################################################### 7 | # Set default behavior for command prompt diff. 8 | # 9 | # This is need for earlier builds of msysgit that does not have it on by 10 | # default for csharp files. 11 | # Note: This is only used by command line 12 | ############################################################################### 13 | #*.cs diff=csharp 14 | 15 | ############################################################################### 16 | # Set the merge driver for project and solution files 17 | # 18 | # Merging from the command prompt will add diff markers to the files if there 19 | # are conflicts (Merging from VS is not affected by the settings below, in VS 20 | # the diff markers are never inserted). Diff markers may cause the following 21 | # file extensions to fail to load in VS. An alternative would be to treat 22 | # these files as binary and thus will always conflict and require user 23 | # intervention with every merge. To do so, just uncomment the entries below 24 | ############################################################################### 25 | #*.sln merge=binary 26 | #*.csproj merge=binary 27 | #*.vbproj merge=binary 28 | #*.vcxproj merge=binary 29 | #*.vcproj merge=binary 30 | #*.dbproj merge=binary 31 | #*.fsproj merge=binary 32 | #*.lsproj merge=binary 33 | #*.wixproj merge=binary 34 | #*.modelproj merge=binary 35 | #*.sqlproj merge=binary 36 | #*.wwaproj merge=binary 37 | 38 | ############################################################################### 39 | # behavior for image files 40 | # 41 | # image files are treated as binary by default. 42 | ############################################################################### 43 | #*.jpg binary 44 | #*.png binary 45 | #*.gif binary 46 | 47 | ############################################################################### 48 | # diff behavior for common document formats 49 | # 50 | # Convert binary document formats to text before diffing them. This feature 51 | # is only available from the command line. Turn it on by uncommenting the 52 | # entries below. 53 | ############################################################################### 54 | #*.doc diff=astextplain 55 | #*.DOC diff=astextplain 56 | #*.docx diff=astextplain 57 | #*.DOCX diff=astextplain 58 | #*.dot diff=astextplain 59 | #*.DOT diff=astextplain 60 | #*.pdf diff=astextplain 61 | #*.PDF diff=astextplain 62 | #*.rtf diff=astextplain 63 | #*.RTF diff=astextplain 64 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | ## Ignore Visual Studio temporary files, build results, and 2 | ## files generated by popular Visual Studio add-ons. 3 | 4 | # User-specific files 5 | *.suo 6 | *.user 7 | *.userosscache 8 | *.sln.docstates 9 | 10 | # User-specific files (MonoDevelop/Xamarin Studio) 11 | *.userprefs 12 | 13 | # Build results 14 | [Dd]ebug/ 15 | [Dd]ebugPublic/ 16 | [Rr]elease/ 17 | [Rr]eleases/ 18 | x64/ 19 | x86/ 20 | bld/ 21 | [Bb]in/ 22 | [Oo]bj/ 23 | [Ll]og/ 24 | 25 | # Visual Studio 2015 cache/options directory 26 | .vs/ 27 | # Uncomment if you have tasks that create the project's static files in wwwroot 28 | #wwwroot/ 29 | 30 | # MSTest test Results 31 | [Tt]est[Rr]esult*/ 32 | [Bb]uild[Ll]og.* 33 | 34 | # NUNIT 35 | *.VisualState.xml 36 | TestResult.xml 37 | 38 | # Build Results of an ATL Project 39 | [Dd]ebugPS/ 40 | [Rr]eleasePS/ 41 | dlldata.c 42 | 43 | # DNX 44 | project.lock.json 45 | project.fragment.lock.json 46 | artifacts/ 47 | 48 | *_i.c 49 | *_p.c 50 | *_i.h 51 | *.ilk 52 | *.meta 53 | *.obj 54 | *.pch 55 | *.pdb 56 | *.pgc 57 | *.pgd 58 | *.rsp 59 | *.sbr 60 | *.tlb 61 | *.tli 62 | *.tlh 63 | *.tmp 64 | *.tmp_proj 65 | *.log 66 | *.vspscc 67 | *.vssscc 68 | .builds 69 | *.pidb 70 | *.svclog 71 | *.scc 72 | 73 | # Chutzpah Test files 74 | _Chutzpah* 75 | 76 | # Visual C++ cache files 77 | ipch/ 78 | *.aps 79 | *.ncb 80 | *.opendb 81 | *.opensdf 82 | *.sdf 83 | *.cachefile 84 | *.VC.db 85 | *.VC.VC.opendb 86 | 87 | # Visual Studio profiler 88 | *.psess 89 | *.vsp 90 | *.vspx 91 | *.sap 92 | 93 | # TFS 2012 Local Workspace 94 | $tf/ 95 | 96 | # Guidance Automation Toolkit 97 | *.gpState 98 | 99 | # ReSharper is a .NET coding add-in 100 | _ReSharper*/ 101 | *.[Rr]e[Ss]harper 102 | *.DotSettings.user 103 | 104 | # JustCode is a .NET coding add-in 105 | .JustCode 106 | 107 | # TeamCity is a build add-in 108 | _TeamCity* 109 | 110 | # DotCover is a Code Coverage Tool 111 | *.dotCover 112 | 113 | # NCrunch 114 | _NCrunch_* 115 | .*crunch*.local.xml 116 | nCrunchTemp_* 117 | 118 | # MightyMoose 119 | *.mm.* 120 | AutoTest.Net/ 121 | 122 | # Web workbench (sass) 123 | .sass-cache/ 124 | 125 | # Installshield output folder 126 | [Ee]xpress/ 127 | 128 | # DocProject is a documentation generator add-in 129 | DocProject/buildhelp/ 130 | DocProject/Help/*.HxT 131 | DocProject/Help/*.HxC 132 | DocProject/Help/*.hhc 133 | DocProject/Help/*.hhk 134 | DocProject/Help/*.hhp 135 | DocProject/Help/Html2 136 | DocProject/Help/html 137 | 138 | # Click-Once directory 139 | publish/ 140 | 141 | # Publish Web Output 142 | *.[Pp]ublish.xml 143 | *.azurePubxml 144 | # TODO: Comment the next line if you want to checkin your web deploy settings 145 | # but database connection strings (with potential passwords) will be unencrypted 146 | #*.pubxml 147 | *.publishproj 148 | 149 | # Microsoft Azure Web App publish settings. Comment the next line if you want to 150 | # checkin your Azure Web App publish settings, but sensitive information contained 151 | # in these scripts will be unencrypted 152 | PublishScripts/ 153 | 154 | # NuGet Packages 155 | *.nupkg 156 | # The packages folder can be ignored because of Package Restore 157 | **/packages/* 158 | # except build/, which is used as an MSBuild target. 159 | !**/packages/build/ 160 | # Uncomment if necessary however generally it will be regenerated when needed 161 | #!**/packages/repositories.config 162 | # NuGet v3's project.json files produces more ignoreable files 163 | *.nuget.props 164 | *.nuget.targets 165 | 166 | # Microsoft Azure Build Output 167 | csx/ 168 | *.build.csdef 169 | 170 | # Microsoft Azure Emulator 171 | ecf/ 172 | rcf/ 173 | 174 | # Windows Store app package directories and files 175 | AppPackages/ 176 | BundleArtifacts/ 177 | Package.StoreAssociation.xml 178 | _pkginfo.txt 179 | 180 | # Visual Studio cache files 181 | # files ending in .cache can be ignored 182 | *.[Cc]ache 183 | # but keep track of directories ending in .cache 184 | !*.[Cc]ache/ 185 | 186 | # Others 187 | ClientBin/ 188 | ~$* 189 | *~ 190 | *.dbmdl 191 | *.dbproj.schemaview 192 | *.jfm 193 | *.pfx 194 | *.publishsettings 195 | node_modules/ 196 | orleans.codegen.cs 197 | 198 | # Since there are multiple workflows, uncomment next line to ignore bower_components 199 | # (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) 200 | #bower_components/ 201 | 202 | # RIA/Silverlight projects 203 | Generated_Code/ 204 | 205 | # Backup & report files from converting an old project file 206 | # to a newer Visual Studio version. Backup files are not needed, 207 | # because we have git ;-) 208 | _UpgradeReport_Files/ 209 | Backup*/ 210 | UpgradeLog*.XML 211 | UpgradeLog*.htm 212 | 213 | # SQL Server files 214 | *.mdf 215 | *.ldf 216 | 217 | # Business Intelligence projects 218 | *.rdl.data 219 | *.bim.layout 220 | *.bim_*.settings 221 | 222 | # Microsoft Fakes 223 | FakesAssemblies/ 224 | 225 | # GhostDoc plugin setting file 226 | *.GhostDoc.xml 227 | 228 | # Node.js Tools for Visual Studio 229 | .ntvs_analysis.dat 230 | 231 | # Visual Studio 6 build log 232 | *.plg 233 | 234 | # Visual Studio 6 workspace options file 235 | *.opt 236 | 237 | # Visual Studio LightSwitch build output 238 | **/*.HTMLClient/GeneratedArtifacts 239 | **/*.DesktopClient/GeneratedArtifacts 240 | **/*.DesktopClient/ModelManifest.xml 241 | **/*.Server/GeneratedArtifacts 242 | **/*.Server/ModelManifest.xml 243 | _Pvt_Extensions 244 | 245 | # Paket dependency manager 246 | .paket/paket.exe 247 | paket-files/ 248 | 249 | # FAKE - F# Make 250 | .fake/ 251 | 252 | # JetBrains Rider 253 | .idea/ 254 | *.sln.iml 255 | 256 | # CodeRush 257 | .cr/ 258 | 259 | # Python Tools for Visual Studio (PTVS) 260 | __pycache__/ 261 | *.pyc -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Client/.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 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Client/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 `<meta>` 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.<br> 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`.<br> 151 | Read instructions below for using assets from JavaScript and HTML. 152 | 153 | You can, however, create more top-level directories.<br> 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.<br> 163 | Open [http://localhost:3000](http://localhost:3000) to view it in the browser. 164 | 165 | The page will reload if you make edits.<br> 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.<br> 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.<br> 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.<br> 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.<br> 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.<br> 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 `<title>` 340 | 341 | You can find the source HTML file in the `public` folder of the generated project. You may edit the `<title>` 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.<br> 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 <Button color="red" />; 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 | <div> 448 | <button onClick={this.handleClick}>Load</button> 449 | </div> 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 <div className="Button" />; 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 `<AcceptButton>` and `<RejectButton>` components, we recommend creating a `<Button>` component with its own `.Button` styles, that both `<AcceptButton>` and `<RejectButton>` 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 <img src={logo} alt="Logo" />; 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).<br> 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 `<script>` tag with the compiled code will be added to it automatically during the build process. 673 | 674 | ### Adding Assets Outside of the Module System 675 | 676 | You can also add other assets to the `public` folder. 677 | 678 | Note that we normally encourage you to `import` assets in JavaScript files instead. 679 | For example, see the sections on [adding a stylesheet](#adding-a-stylesheet) and [adding images and fonts](#adding-images-fonts-and-files). 680 | This mechanism provides a number of benefits: 681 | 682 | * Scripts and stylesheets get minified and bundled together to avoid extra network requests. 683 | * Missing files cause compilation errors instead of 404 errors for your users. 684 | * Result filenames include content hashes so you don’t need to worry about browsers caching their old versions. 685 | 686 | However there is an **escape hatch** that you can use to add an asset outside of the module system. 687 | 688 | If you put a file into the `public` folder, it will **not** be processed by Webpack. Instead it will be copied into the build folder untouched. To reference assets in the `public` folder, you need to use a special variable called `PUBLIC_URL`. 689 | 690 | Inside `index.html`, you can use it like this: 691 | 692 | ```html 693 | <link rel="shortcut icon" href="%PUBLIC_URL%/favicon.ico"> 694 | ``` 695 | 696 | Only files inside the `public` folder will be accessible by `%PUBLIC_URL%` prefix. If you need to use a file from `src` or `node_modules`, you’ll have to copy it there to explicitly specify your intention to make this file a part of the build. 697 | 698 | When you run `npm run build`, Create React App will substitute `%PUBLIC_URL%` with a correct absolute path so your project works even if you use client-side routing or host it at a non-root URL. 699 | 700 | In JavaScript code, you can use `process.env.PUBLIC_URL` for similar purposes: 701 | 702 | ```js 703 | render() { 704 | // Note: this is an escape hatch and should be used sparingly! 705 | // Normally we recommend using `import` for getting asset URLs 706 | // as described in “Adding Images and Fonts” above this section. 707 | return <img src={process.env.PUBLIC_URL + '/img/logo.png'} />; 708 | } 709 | ``` 710 | 711 | Keep in mind the downsides of this approach: 712 | 713 | * None of the files in `public` folder get post-processed or minified. 714 | * Missing files will not be called at compilation time, and will cause 404 errors for your users. 715 | * Result filenames won’t include content hashes so you’ll need to add query arguments or rename them every time they change. 716 | 717 | ### When to Use the `public` Folder 718 | 719 | Normally we recommend importing [stylesheets](#adding-a-stylesheet), [images, and fonts](#adding-images-fonts-and-files) from JavaScript. 720 | The `public` folder is useful as a workaround for a number of less common cases: 721 | 722 | * You need a file with a specific name in the build output, such as [`manifest.webmanifest`](https://developer.mozilla.org/en-US/docs/Web/Manifest). 723 | * You have thousands of images and need to dynamically reference their paths. 724 | * You want to include a small script like [`pace.js`](http://github.hubspot.com/pace/docs/welcome/) outside of the bundled code. 725 | * Some library may be incompatible with Webpack and you have no other option but to include it as a `<script>` tag. 726 | 727 | Note that if you add a `<script>` that declares global variables, you also need to read the next section on using them. 728 | 729 | ## Using Global Variables 730 | 731 | When you include a script in the HTML file that defines global variables and try to use one of these variables in the code, the linter will complain because it cannot see the definition of the variable. 732 | 733 | You can avoid this by reading the global variable explicitly from the `window` object, for example: 734 | 735 | ```js 736 | const $ = window.$; 737 | ``` 738 | 739 | This makes it obvious you are using a global variable intentionally rather than because of a typo. 740 | 741 | Alternatively, you can force the linter to ignore any line by adding `// eslint-disable-line` after it. 742 | 743 | ## Adding Bootstrap 744 | 745 | You don’t have to use [React Bootstrap](https://react-bootstrap.github.io) together with React but it is a popular library for integrating Bootstrap with React apps. If you need it, you can integrate it with Create React App by following these steps: 746 | 747 | Install React Bootstrap and Bootstrap from npm. React Bootstrap does not include Bootstrap CSS so this needs to be installed as well: 748 | 749 | ```sh 750 | npm install --save react-bootstrap bootstrap@3 751 | ``` 752 | 753 | Alternatively you may use `yarn`: 754 | 755 | ```sh 756 | yarn add react-bootstrap bootstrap@3 757 | ``` 758 | 759 | Import Bootstrap CSS and optionally Bootstrap theme CSS in the beginning of your ```src/index.js``` file: 760 | 761 | ```js 762 | import 'bootstrap/dist/css/bootstrap.css'; 763 | import 'bootstrap/dist/css/bootstrap-theme.css'; 764 | // Put any other imports below so that CSS from your 765 | // components takes precedence over default styles. 766 | ``` 767 | 768 | Import required React Bootstrap components within ```src/App.js``` file or your custom component files: 769 | 770 | ```js 771 | import { Navbar, Jumbotron, Button } from 'react-bootstrap'; 772 | ``` 773 | 774 | Now you are ready to use the imported React Bootstrap components within your component hierarchy defined in the render method. Here is an example [`App.js`](https://gist.githubusercontent.com/gaearon/85d8c067f6af1e56277c82d19fd4da7b/raw/6158dd991b67284e9fc8d70b9d973efe87659d72/App.js) redone using React Bootstrap. 775 | 776 | ### Using a Custom Theme 777 | 778 | Sometimes you might need to tweak the visual styles of Bootstrap (or equivalent package).<br> 779 | We suggest the following approach: 780 | 781 | * Create a new package that depends on the package you wish to customize, e.g. Bootstrap. 782 | * Add the necessary build steps to tweak the theme, and publish your package on npm. 783 | * Install your own theme npm package as a dependency of your app. 784 | 785 | Here is an example of adding a [customized Bootstrap](https://medium.com/@tacomanator/customizing-create-react-app-aa9ffb88165) that follows these steps. 786 | 787 | ## Adding Flow 788 | 789 | Flow is a static type checker that helps you write code with fewer bugs. Check out this [introduction to using static types in JavaScript](https://medium.com/@preethikasireddy/why-use-static-types-in-javascript-part-1-8382da1e0adb) if you are new to this concept. 790 | 791 | Recent versions of [Flow](http://flowtype.org/) work with Create React App projects out of the box. 792 | 793 | To add Flow to a Create React App project, follow these steps: 794 | 795 | 1. Run `npm install --save flow-bin` (or `yarn add flow-bin`). 796 | 2. Add `"flow": "flow"` to the `scripts` section of your `package.json`. 797 | 3. Run `npm run flow init` (or `yarn flow init`) to create a [`.flowconfig` file](https://flowtype.org/docs/advanced-configuration.html) in the root directory. 798 | 4. Add `// @flow` to any files you want to type check (for example, to `src/App.js`). 799 | 800 | Now you can run `npm run flow` (or `yarn flow`) to check the files for type errors. 801 | You can optionally use an IDE like [Nuclide](https://nuclide.io/docs/languages/flow/) for a better integrated experience. 802 | In the future we plan to integrate it into Create React App even more closely. 803 | 804 | To learn more about Flow, check out [its documentation](https://flowtype.org/). 805 | 806 | ## Adding Custom Environment Variables 807 | 808 | >Note: this feature is available with `react-scripts@0.2.3` and higher. 809 | 810 | Your project can consume variables declared in your environment as if they were declared locally in your JS files. By 811 | default you will have `NODE_ENV` defined for you, and any other environment variables starting with 812 | `REACT_APP_`. 813 | 814 | **The environment variables are embedded during the build time**. Since Create React App produces a static HTML/CSS/JS bundle, it can’t possibly read them at runtime. To read them at runtime, you would need to load HTML into memory on the server and replace placeholders in runtime, just like [described here](#injecting-data-from-the-server-into-the-page). Alternatively you can rebuild the app on the server anytime you change them. 815 | 816 | >Note: You must create custom environment variables beginning with `REACT_APP_`. Any other variables except `NODE_ENV` will be ignored to avoid accidentally [exposing a private key on the machine that could have the same name](https://github.com/facebookincubator/create-react-app/issues/865#issuecomment-252199527). Changing any environment variables will require you to restart the development server if it is running. 817 | 818 | These environment variables will be defined for you on `process.env`. For example, having an environment 819 | variable named `REACT_APP_SECRET_CODE` will be exposed in your JS as `process.env.REACT_APP_SECRET_CODE`. 820 | 821 | There is also a special built-in environment variable called `NODE_ENV`. You can read it from `process.env.NODE_ENV`. When you run `npm start`, it is always equal to `'development'`, when you run `npm test` it is always equal to `'test'`, and when you run `npm run build` to make a production bundle, it is always equal to `'production'`. **You cannot override `NODE_ENV` manually.** This prevents developers from accidentally deploying a slow development build to production. 822 | 823 | These environment variables can be useful for displaying information conditionally based on where the project is 824 | deployed or consuming sensitive data that lives outside of version control. 825 | 826 | First, you need to have environment variables defined. For example, let’s say you wanted to consume a secret defined 827 | in the environment inside a `<form>`: 828 | 829 | ```jsx 830 | render() { 831 | return ( 832 | <div> 833 | <small>You are running this application in <b>{process.env.NODE_ENV}</b> mode.</small> 834 | <form> 835 | <input type="hidden" defaultValue={process.env.REACT_APP_SECRET_CODE} /> 836 | </form> 837 | </div> 838 | ); 839 | } 840 | ``` 841 | 842 | During the build, `process.env.REACT_APP_SECRET_CODE` will be replaced with the current value of the `REACT_APP_SECRET_CODE` environment variable. Remember that the `NODE_ENV` variable will be set for you automatically. 843 | 844 | When you load the app in the browser and inspect the `<input>`, you will see its value set to `abcdef`, and the bold text will show the environment provided when using `npm start`: 845 | 846 | ```html 847 | <div> 848 | <small>You are running this application in <b>development</b> mode.</small> 849 | <form> 850 | <input type="hidden" value="abcdef" /> 851 | </form> 852 | </div> 853 | ``` 854 | 855 | The above form is looking for a variable called `REACT_APP_SECRET_CODE` from the environment. In order to consume this 856 | value, we need to have it defined in the environment. This can be done using two ways: either in your shell or in 857 | a `.env` file. Both of these ways are described in the next few sections. 858 | 859 | Having access to the `NODE_ENV` is also useful for performing actions conditionally: 860 | 861 | ```js 862 | if (process.env.NODE_ENV !== 'production') { 863 | analytics.disable(); 864 | } 865 | ``` 866 | 867 | When you compile the app with `npm run build`, the minification step will strip out this condition, and the resulting bundle will be smaller. 868 | 869 | ### Referencing Environment Variables in the HTML 870 | 871 | >Note: this feature is available with `react-scripts@0.9.0` and higher. 872 | 873 | You can also access the environment variables starting with `REACT_APP_` in the `public/index.html`. For example: 874 | 875 | ```html 876 | <title>%REACT_APP_WEBSITE_NAME% 877 | ``` 878 | 879 | Note that the caveats from the above section apply: 880 | 881 | * Apart from a few built-in variables (`NODE_ENV` and `PUBLIC_URL`), variable names must start with `REACT_APP_` to work. 882 | * The environment variables are injected at build time. If you need to inject them at runtime, [follow this approach instead](#generating-dynamic-meta-tags-on-the-server). 883 | 884 | ### Adding Temporary Environment Variables In Your Shell 885 | 886 | Defining environment variables can vary between OSes. It’s also important to know that this manner is temporary for the 887 | life of the shell session. 888 | 889 | #### Windows (cmd.exe) 890 | 891 | ```cmd 892 | set REACT_APP_SECRET_CODE=abcdef&&npm start 893 | ``` 894 | 895 | (Note: the lack of whitespace is intentional.) 896 | 897 | #### Linux, macOS (Bash) 898 | 899 | ```bash 900 | REACT_APP_SECRET_CODE=abcdef npm start 901 | ``` 902 | 903 | ### Adding Development Environment Variables In `.env` 904 | 905 | >Note: this feature is available with `react-scripts@0.5.0` and higher. 906 | 907 | To define permanent environment variables, create a file called `.env` in the root of your project: 908 | 909 | ``` 910 | REACT_APP_SECRET_CODE=abcdef 911 | ``` 912 | 913 | `.env` files **should be** checked into source control (with the exclusion of `.env*.local`). 914 | 915 | #### What other `.env` files can be used? 916 | 917 | >Note: this feature is **available with `react-scripts@1.0.0` and higher**. 918 | 919 | * `.env`: Default. 920 | * `.env.local`: Local overrides. **This file is loaded for all environments except test.** 921 | * `.env.development`, `.env.test`, `.env.production`: Environment-specific settings. 922 | * `.env.development.local`, `.env.test.local`, `.env.production.local`: Local overrides of environment-specific settings. 923 | 924 | Files on the left have more priority than files on the right: 925 | 926 | * `npm start`: `.env.development.local`, `.env.development`, `.env.local`, `.env` 927 | * `npm run build`: `.env.production.local`, `.env.production`, `.env.local`, `.env` 928 | * `npm test`: `.env.test.local`, `.env.test`, `.env` (note `.env.local` is missing) 929 | 930 | These variables will act as the defaults if the machine does not explicitly set them.
931 | Please refer to the [dotenv documentation](https://github.com/motdotla/dotenv) for more details. 932 | 933 | >Note: If you are defining environment variables for development, your CI and/or hosting platform will most likely need 934 | these defined as well. Consult their documentation how to do this. For example, see the documentation for [Travis CI](https://docs.travis-ci.com/user/environment-variables/) or [Heroku](https://devcenter.heroku.com/articles/config-vars). 935 | 936 | ## Can I Use Decorators? 937 | 938 | Many popular libraries use [decorators](https://medium.com/google-developers/exploring-es7-decorators-76ecb65fb841) in their documentation.
939 | Create React App doesn’t support decorator syntax at the moment because: 940 | 941 | * It is an experimental proposal and is subject to change. 942 | * The current specification version is not officially supported by Babel. 943 | * If the specification changes, we won’t be able to write a codemod because we don’t use them internally at Facebook. 944 | 945 | However in many cases you can rewrite decorator-based code without decorators just as fine.
946 | Please refer to these two threads for reference: 947 | 948 | * [#214](https://github.com/facebookincubator/create-react-app/issues/214) 949 | * [#411](https://github.com/facebookincubator/create-react-app/issues/411) 950 | 951 | Create React App will add decorator support when the specification advances to a stable stage. 952 | 953 | ## Integrating with an API Backend 954 | 955 | These tutorials will help you to integrate your app with an API backend running on another port, 956 | using `fetch()` to access it. 957 | 958 | ### Node 959 | Check out [this tutorial](https://www.fullstackreact.com/articles/using-create-react-app-with-a-server/). 960 | You can find the companion GitHub repository [here](https://github.com/fullstackreact/food-lookup-demo). 961 | 962 | ### Ruby on Rails 963 | 964 | Check out [this tutorial](https://www.fullstackreact.com/articles/how-to-get-create-react-app-to-work-with-your-rails-api/). 965 | You can find the companion GitHub repository [here](https://github.com/fullstackreact/food-lookup-demo-rails). 966 | 967 | ## Proxying API Requests in Development 968 | 969 | >Note: this feature is available with `react-scripts@0.2.3` and higher. 970 | 971 | People often serve the front-end React app from the same host and port as their backend implementation.
972 | For example, a production setup might look like this after the app is deployed: 973 | 974 | ``` 975 | / - static server returns index.html with React app 976 | /todos - static server returns index.html with React app 977 | /api/todos - server handles any /api/* requests using the backend implementation 978 | ``` 979 | 980 | Such setup is **not** required. However, if you **do** have a setup like this, it is convenient to write requests like `fetch('/api/todos')` without worrying about redirecting them to another host or port during development. 981 | 982 | To tell the development server to proxy any unknown requests to your API server in development, add a `proxy` field to your `package.json`, for example: 983 | 984 | ```js 985 | "proxy": "http://localhost:4000", 986 | ``` 987 | 988 | This way, when you `fetch('/api/todos')` in development, the development server will recognize that it’s not a static asset, and will proxy your request to `http://localhost:4000/api/todos` as a fallback. The development server will **only** attempt to send requests without `text/html` in its `Accept` header to the proxy. 989 | 990 | Conveniently, this avoids [CORS issues](http://stackoverflow.com/questions/21854516/understanding-ajax-cors-and-security-considerations) and error messages like this in development: 991 | 992 | ``` 993 | Fetch API cannot load http://localhost:4000/api/todos. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. 994 | ``` 995 | 996 | Keep in mind that `proxy` only has effect in development (with `npm start`), and it is up to you to ensure that URLs like `/api/todos` point to the right thing in production. You don’t have to use the `/api` prefix. Any unrecognized request without a `text/html` accept header will be redirected to the specified `proxy`. 997 | 998 | The `proxy` option supports HTTP, HTTPS and WebSocket connections.
999 | If the `proxy` option is **not** flexible enough for you, alternatively you can: 1000 | 1001 | * [Configure the proxy yourself](#configuring-the-proxy-manually) 1002 | * Enable CORS on your server ([here’s how to do it for Express](http://enable-cors.org/server_expressjs.html)). 1003 | * Use [environment variables](#adding-custom-environment-variables) to inject the right server host and port into your app. 1004 | 1005 | ### "Invalid Host Header" Errors After Configuring Proxy 1006 | 1007 | When you enable the `proxy` option, you opt into a more strict set of host checks. This is necessary because leaving the backend open to remote hosts makes your computer vulnerable to DNS rebinding attacks. The issue is explained in [this article](https://medium.com/webpack/webpack-dev-server-middleware-security-issues-1489d950874a) and [this issue](https://github.com/webpack/webpack-dev-server/issues/887). 1008 | 1009 | This shouldn’t affect you when developing on `localhost`, but if you develop remotely like [described here](https://github.com/facebookincubator/create-react-app/issues/2271), you will see this error in the browser after enabling the `proxy` option: 1010 | 1011 | >Invalid Host header 1012 | 1013 | To work around it, you can specify your public development host in a file called `.env.development` in the root of your project: 1014 | 1015 | ``` 1016 | HOST=mypublicdevhost.com 1017 | ``` 1018 | 1019 | If you restart the development server now and load the app from the specified host, it should work. 1020 | 1021 | If you are still having issues or if you’re using a more exotic environment like a cloud editor, you can bypass the host check completely by adding a line to `.env.development.local`. **Note that this is dangerous and exposes your machine to remote code execution from malicious websites:** 1022 | 1023 | ``` 1024 | # NOTE: THIS IS DANGEROUS! 1025 | # It exposes your machine to attacks from the websites you visit. 1026 | DANGEROUSLY_DISABLE_HOST_CHECK=true 1027 | ``` 1028 | 1029 | We don’t recommend this approach. 1030 | 1031 | ### Configuring the Proxy Manually 1032 | 1033 | >Note: this feature is available with `react-scripts@1.0.0` and higher. 1034 | 1035 | If the `proxy` option is **not** flexible enough for you, you can specify an object in the following form (in `package.json`).
1036 | You may also specify any configuration value [`http-proxy-middleware`](https://github.com/chimurai/http-proxy-middleware#options) or [`http-proxy`](https://github.com/nodejitsu/node-http-proxy#options) supports. 1037 | ```js 1038 | { 1039 | // ... 1040 | "proxy": { 1041 | "/api": { 1042 | "target": "", 1043 | "ws": true 1044 | // ... 1045 | } 1046 | } 1047 | // ... 1048 | } 1049 | ``` 1050 | 1051 | All requests matching this path will be proxies, no exceptions. This includes requests for `text/html`, which the standard `proxy` option does not proxy. 1052 | 1053 | If you need to specify multiple proxies, you may do so by specifying additional entries. 1054 | Matches are regular expressions, so that you can use a regexp to match multiple paths. 1055 | ```js 1056 | { 1057 | // ... 1058 | "proxy": { 1059 | // Matches any request starting with /api 1060 | "/api": { 1061 | "target": "", 1062 | "ws": true 1063 | // ... 1064 | }, 1065 | // Matches any request starting with /foo 1066 | "/foo": { 1067 | "target": "", 1068 | "ssl": true, 1069 | "pathRewrite": { 1070 | "^/foo": "/foo/beta" 1071 | } 1072 | // ... 1073 | }, 1074 | // Matches /bar/abc.html but not /bar/sub/def.html 1075 | "/bar/[^/]*[.]html": { 1076 | "target": "", 1077 | // ... 1078 | }, 1079 | // Matches /baz/abc.html and /baz/sub/def.html 1080 | "/baz/.*/.*[.]html": { 1081 | "target": "" 1082 | // ... 1083 | } 1084 | } 1085 | // ... 1086 | } 1087 | ``` 1088 | 1089 | ### Configuring a WebSocket Proxy 1090 | 1091 | When setting up a WebSocket proxy, there are a some extra considerations to be aware of. 1092 | 1093 | If you’re using a WebSocket engine like [Socket.io](https://socket.io/), you must have a Socket.io server running that you can use as the proxy target. Socket.io will not work with a standard WebSocket server. Specifically, don't expect Socket.io to work with [the websocket.org echo test](http://websocket.org/echo.html). 1094 | 1095 | There’s some good documentation available for [setting up a Socket.io server](https://socket.io/docs/). 1096 | 1097 | Standard WebSockets **will** work with a standard WebSocket server as well as the websocket.org echo test. You can use libraries like [ws](https://github.com/websockets/ws) for the server, with [native WebSockets in the browser](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket). 1098 | 1099 | Either way, you can proxy WebSocket requests manually in `package.json`: 1100 | 1101 | ```js 1102 | { 1103 | // ... 1104 | "proxy": { 1105 | "/socket": { 1106 | // Your compatible WebSocket server 1107 | "target": "ws://", 1108 | // Tell http-proxy-middleware that this is a WebSocket proxy. 1109 | // Also allows you to proxy WebSocket requests without an additional HTTP request 1110 | // https://github.com/chimurai/http-proxy-middleware#external-websocket-upgrade 1111 | "ws": true 1112 | // ... 1113 | } 1114 | } 1115 | // ... 1116 | } 1117 | ``` 1118 | 1119 | ## Using HTTPS in Development 1120 | 1121 | >Note: this feature is available with `react-scripts@0.4.0` and higher. 1122 | 1123 | You may require the dev server to serve pages over HTTPS. One particular case where this could be useful is when using [the "proxy" feature](#proxying-api-requests-in-development) to proxy requests to an API server when that API server is itself serving HTTPS. 1124 | 1125 | To do this, set the `HTTPS` environment variable to `true`, then start the dev server as usual with `npm start`: 1126 | 1127 | #### Windows (cmd.exe) 1128 | 1129 | ```cmd 1130 | set HTTPS=true&&npm start 1131 | ``` 1132 | 1133 | (Note: the lack of whitespace is intentional.) 1134 | 1135 | #### Linux, macOS (Bash) 1136 | 1137 | ```bash 1138 | HTTPS=true npm start 1139 | ``` 1140 | 1141 | Note that the server will use a self-signed certificate, so your web browser will almost definitely display a warning upon accessing the page. 1142 | 1143 | ## Generating Dynamic `` Tags on the Server 1144 | 1145 | Since Create React App doesn’t support server rendering, you might be wondering how to make `` tags dynamic and reflect the current URL. To solve this, we recommend to add placeholders into the HTML, like this: 1146 | 1147 | ```html 1148 | 1149 | 1150 | 1151 | 1152 | 1153 | ``` 1154 | 1155 | Then, on the server, regardless of the backend you use, you can read `index.html` into memory and replace `__OG_TITLE__`, `__OG_DESCRIPTION__`, and any other placeholders with values depending on the current URL. Just make sure to sanitize and escape the interpolated values so that they are safe to embed into HTML! 1156 | 1157 | If you use a Node server, you can even share the route matching logic between the client and the server. However duplicating it also works fine in simple cases. 1158 | 1159 | ## Pre-Rendering into Static HTML Files 1160 | 1161 | If you’re hosting your `build` with a static hosting provider you can use [react-snapshot](https://www.npmjs.com/package/react-snapshot) or [react-snap](https://github.com/stereobooster/react-snap) to generate HTML pages for each route, or relative link, in your application. These pages will then seamlessly become active, or “hydrated”, when the JavaScript bundle has loaded. 1162 | 1163 | There are also opportunities to use this outside of static hosting, to take the pressure off the server when generating and caching routes. 1164 | 1165 | The primary benefit of pre-rendering is that you get the core content of each page _with_ the HTML payload—regardless of whether or not your JavaScript bundle successfully downloads. It also increases the likelihood that each route of your application will be picked up by search engines. 1166 | 1167 | You can read more about [zero-configuration pre-rendering (also called snapshotting) here](https://medium.com/superhighfives/an-almost-static-stack-6df0a2791319). 1168 | 1169 | ## Injecting Data from the Server into the Page 1170 | 1171 | Similarly to the previous section, you can leave some placeholders in the HTML that inject global variables, for example: 1172 | 1173 | ```js 1174 | 1175 | 1176 | 1177 | 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 | ![Jest watch mode](http://facebook.github.io/jest/img/blog/15-watch.gif) 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 ` 54 | 55 |
56 | {this.state.messages.map((message, index) => ( 57 | {message} 58 | ))} 59 |
60 | 61 | ); 62 | } 63 | } 64 | 65 | export default Chat; 66 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Client/src/index.css: -------------------------------------------------------------------------------- 1 | body { 2 | margin: 0; 3 | padding: 0; 4 | font-family: sans-serif; 5 | } 6 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Client/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 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Client/src/logo.svg: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Client/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 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Server/AspNetCoreSignalR_React.Server.csproj: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | netcoreapp3.1 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Server/ChatHub.cs: -------------------------------------------------------------------------------- 1 | using Microsoft.AspNetCore.SignalR; 2 | using System.Threading.Tasks; 3 | 4 | namespace AspNetCoreSignalR_React.Server 5 | { 6 | public class ChatHub : Hub 7 | { 8 | public async Task SendToAll(string name, string message) 9 | { 10 | await Clients.All.SendAsync("sendToAll", name, message); 11 | } 12 | } 13 | } -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Server/Program.cs: -------------------------------------------------------------------------------- 1 | using Microsoft.AspNetCore; 2 | using Microsoft.AspNetCore.Hosting; 3 | 4 | namespace AspNetCoreSignalR_React.Server 5 | { 6 | public class Program 7 | { 8 | public static void Main(string[] args) 9 | { 10 | BuildWebHost(args).Run(); 11 | } 12 | 13 | public static IWebHost BuildWebHost(string[] args) => 14 | WebHost.CreateDefaultBuilder(args) 15 | .UseStartup() 16 | .Build(); 17 | } 18 | } 19 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Server/Properties/launchSettings.json: -------------------------------------------------------------------------------- 1 | { 2 | "iisSettings": { 3 | "windowsAuthentication": false, 4 | "anonymousAuthentication": true, 5 | "iisExpress": { 6 | "applicationUrl": "http://localhost:5000/", 7 | "sslPort": 0 8 | } 9 | }, 10 | "profiles": { 11 | "IIS Express": { 12 | "commandName": "IISExpress", 13 | "launchBrowser": true, 14 | "environmentVariables": { 15 | "ASPNETCORE_ENVIRONMENT": "Development" 16 | } 17 | }, 18 | "AngularAspNetCoreSignalR": { 19 | "commandName": "Project", 20 | "launchBrowser": true, 21 | "environmentVariables": { 22 | "ASPNETCORE_ENVIRONMENT": "Development" 23 | }, 24 | "applicationUrl": "http://localhost:5000/" 25 | } 26 | } 27 | } 28 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.Server/Startup.cs: -------------------------------------------------------------------------------- 1 | using Microsoft.AspNetCore.Builder; 2 | using Microsoft.AspNetCore.Hosting; 3 | using Microsoft.Extensions.DependencyInjection; 4 | 5 | namespace AspNetCoreSignalR_React.Server 6 | { 7 | public class Startup 8 | { 9 | // This method gets called by the runtime. Use this method to add services to the container. 10 | // For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940 11 | public void ConfigureServices(IServiceCollection services) 12 | { 13 | services.AddCors(o => o.AddPolicy("CorsPolicy", builder => 14 | { 15 | builder 16 | .AllowAnyMethod() 17 | .AllowAnyHeader() 18 | .AllowCredentials() 19 | .WithOrigins("http://localhost:3000"); 20 | })); 21 | 22 | services.AddSignalR(); 23 | } 24 | 25 | // This method gets called by the runtime. Use this method to configure the HTTP request pipeline. 26 | public void Configure(IApplicationBuilder app, IWebHostEnvironment env) 27 | { 28 | app.UseRouting(); 29 | app.UseCors("CorsPolicy"); 30 | 31 | app.UseEndpoints(routes => 32 | { 33 | routes.MapHub("chat"); 34 | }); 35 | } 36 | } 37 | } 38 | -------------------------------------------------------------------------------- /AspNetCoreSignalR_React.sln: -------------------------------------------------------------------------------- 1 |  2 | Microsoft Visual Studio Solution File, Format Version 12.00 3 | # Visual Studio 15 4 | VisualStudioVersion = 15.0.27004.2009 5 | MinimumVisualStudioVersion = 10.0.40219.1 6 | Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "AspNetCoreSignalR_React.Server", "AspNetCoreSignalR_React.Server\AspNetCoreSignalR_React.Server.csproj", "{DB011707-E2FA-4CD5-AB4F-9494863F98E7}" 7 | EndProject 8 | Global 9 | GlobalSection(SolutionConfigurationPlatforms) = preSolution 10 | Debug|Any CPU = Debug|Any CPU 11 | Release|Any CPU = Release|Any CPU 12 | EndGlobalSection 13 | GlobalSection(ProjectConfigurationPlatforms) = postSolution 14 | {DB011707-E2FA-4CD5-AB4F-9494863F98E7}.Debug|Any CPU.ActiveCfg = Debug|Any CPU 15 | {DB011707-E2FA-4CD5-AB4F-9494863F98E7}.Debug|Any CPU.Build.0 = Debug|Any CPU 16 | {DB011707-E2FA-4CD5-AB4F-9494863F98E7}.Release|Any CPU.ActiveCfg = Release|Any CPU 17 | {DB011707-E2FA-4CD5-AB4F-9494863F98E7}.Release|Any CPU.Build.0 = Release|Any CPU 18 | EndGlobalSection 19 | GlobalSection(SolutionProperties) = preSolution 20 | HideSolutionNode = FALSE 21 | EndGlobalSection 22 | GlobalSection(ExtensibilityGlobals) = postSolution 23 | SolutionGuid = {AA2CC289-896F-489A-B1D0-11265B496B12} 24 | EndGlobalSection 25 | EndGlobal 26 | --------------------------------------------------------------------------------