\nYou 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.\nNote that normally you wouldn’t edit files in the public folder very often. For example, adding a stylesheet is done without touching the HTML.\nIf you need to dynamically update the page title based on the content, you can use the browser document.title API. For more complex scenarios when you want to change the title from React components, you can use React Helmet, a third party library.\nIf 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. Alternatively, you can pre-build each page as a static HTML file which then loads the JavaScript bundle, which is covered here.\nInstalling a Dependency\nThe 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:\nAlternatively you may use yarn:\nThis works for any library, not just react-router.\nImporting a Component\nThis project setup supports ES6 modules thanks to Babel.\nWhile you can still use require() and module.exports, we encourage you to use import and export instead.\nFor example:\nButton.js\nDangerButton.js\nBe aware of the difference between default and named exports. It is a common source of mistakes.\nWe 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'.\nNamed 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.\nLearn more about ES6 modules:\nCode Splitting\nInstead 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.\nThis project setup supports code splitting via dynamic import(). Its proposal is in stage 3. The import() function-like form takes the module name as an argument and returns a Promise which always resolves to the namespace object of the module.\nHere is an example:\nmoduleA.js\nApp.js\nThis will make moduleA.js and all its unique dependencies as a separate chunk that only loads after the user clicks the 'Load' button.\nYou can also use it with async / await syntax if you prefer it.\nWith React Router\nIf you are using React Router check out this tutorial on how to use code splitting with it. You can find the companion GitHub repository here.\nAlso check out the Code Splitting section in React documentation.\nAdding a Stylesheet\nThis project setup uses Webpack 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:\nButton.css\nButton.js\nThis is not required for React but many people find this feature convenient. You can read about the benefits of this approach here. However you should be aware that this makes your code less portable to other build tools and environments than Webpack.\nIn 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.\nIf 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.\nPost-Processing CSS\nThis project setup minifies your CSS and adds vendor prefixes to it automatically through Autoprefixer so you don’t need to worry about it.\nFor example, this:\nbecomes this:\nIf you need to disable autoprefixing for some reason, follow this section.\nAdding a CSS Preprocessor (Sass, Less etc.)\nGenerally, 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).\nFollowing 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.\nFirst, let’s install the command-line interface for Sass:\nAlternatively you may use yarn:\nThen in package.json, add the following lines to scripts:\nNote: To use a different preprocessor, replace build-css and watch-css commands according to your preprocessor’s documentation.\nNow 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.\nTo 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.\nTo enable importing files without using relative paths, you can add the --include-path option to the command in package.json.\nThis will allow you to do imports like\nAt 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.\nAs 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:\nAlternatively you may use yarn:\nThen we can change start and build scripts to include the CSS preprocessor commands:\nNow running npm start and npm run build also builds Sass files.\nWhy node-sass-chokidar?\nnode-sass has been reported as having the following issues:\nnode-sass --watch has been reported to have performance issues in certain conditions when used in a virtual machine or with docker.\nInfinite styles compiling #1939\nnode-sass has been reported as having issues with detecting new files in a directory #1891\nnode-sass-chokidar is used here as it addresses these issues.\nAdding Images, Fonts, and Files\nWith Webpack, using static assets like images and fonts works similarly to CSS.\nYou 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.\nTo reduce the number of requests to the server, importing images that are less than 10,000 bytes returns a data URI instead of a path. This applies to the following file extensions: bmp, gif, jpg, jpeg, and png. SVG files are excluded due to #1153.\nHere is an example:\nThis ensures that when the project is built, Webpack will correctly move the images into the build folder, and provide us with correct paths.\nThis works in CSS too:\nWebpack 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.\nPlease be advised that this is also a custom feature of Webpack.\nIt is not required for React but many people enjoy it (and React Native uses a similar mechanism for images).\nAn alternative way of handling static assets is described in the next section.\nUsing the public Folder\nNote: this feature is available with react-scripts@0.5.0 and higher.\nChanging the HTML\nThe public folder contains the HTML file so you can tweak it, for example, to set the page title.\nThe <script> tag with the compiled code will be added to it automatically during the build process.\nAdding Assets Outside of the Module System\nYou can also add other assets to the public folder.\nNote that we normally encourage you to import assets in JavaScript files instead.\nFor example, see the sections on adding a stylesheet and adding images and fonts.\nThis mechanism provides a number of benefits:\nHowever there is an escape hatch that you can use to add an asset outside of the module system.\nIf 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.\nInside index.html, you can use it like this:\nOnly 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.\nWhen 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.\nIn JavaScript code, you can use process.env.PUBLIC_URL for similar purposes:\nKeep in mind the downsides of this approach:\nWhen to Use the public Folder\nNormally we recommend importing stylesheets, images, and fonts from JavaScript.\nThe public folder is useful as a workaround for a number of less common cases:\nNote that if you add a <script> that declares global variables, you also need to read the next section on using them.\nUsing Global Variables\nWhen 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.\nYou can avoid this by reading the global variable explicitly from the window object, for example:\nThis makes it obvious you are using a global variable intentionally rather than because of a typo.\nAlternatively, you can force the linter to ignore any line by adding // eslint-disable-line after it.\nAdding Bootstrap\nYou don’t have to use React Bootstrap 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:\nInstall React Bootstrap and Bootstrap from npm. React Bootstrap does not include Bootstrap CSS so this needs to be installed as well:\nAlternatively you may use yarn:\nImport Bootstrap CSS and optionally Bootstrap theme CSS in the beginning of your src/index.js file:\nImport required React Bootstrap components within src/App.js file or your custom component files:\nNow 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 redone using React Bootstrap.\nUsing a Custom Theme\nSometimes you might need to tweak the visual styles of Bootstrap (or equivalent package).\nWe suggest the following approach:\nHere is an example of adding a customized Bootstrap that follows these steps.\nAdding Flow\nFlow is a static type checker that helps you write code with fewer bugs. Check out this introduction to using static types in JavaScript if you are new to this concept.\nRecent versions of Flow work with Create React App projects out of the box.\nTo add Flow to a Create React App project, follow these steps:\nNow you can run npm run flow (or yarn flow) to check the files for type errors.\nYou can optionally use an IDE like Nuclide for a better integrated experience.\nIn the future we plan to integrate it into Create React App even more closely.\nTo learn more about Flow, check out its documentation.\nAdding a Router\nCreate React App doesn't prescribe a specific routing solution, but React Router is the most popular one.\nTo add it, run:\nAlternatively you may use yarn:\nTo try it, delete all the code in src/App.js and replace it with any of the examples on its website. The Basic Example is a good place to get started.\nNote that you may need to configure your production server to support client-side routing before deploying your app.\nAdding Custom Environment Variables\nNote: this feature is available with react-scripts@0.2.3 and higher.\nYour project can consume variables declared in your environment as if they were declared locally in your JS files. By\ndefault you will have NODE_ENV defined for you, and any other environment variables starting with\nREACT_APP_.\nThe 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. Alternatively you can rebuild the app on the server anytime you change them.\nNote: 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. Changing any environment variables will require you to restart the development server if it is running.\nThese environment variables will be defined for you on process.env. For example, having an environment\nvariable named REACT_APP_SECRET_CODE will be exposed in your JS as process.env.REACT_APP_SECRET_CODE.\nThere 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.\nThese environment variables can be useful for displaying information conditionally based on where the project is\ndeployed or consuming sensitive data that lives outside of version control.\nFirst, you need to have environment variables defined. For example, let’s say you wanted to consume a secret defined\nin the environment inside a <form>:\nDuring 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.\nWhen 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:\nThe above form is looking for a variable called REACT_APP_SECRET_CODE from the environment. In order to consume this\nvalue, we need to have it defined in the environment. This can be done using two ways: either in your shell or in\na .env file. Both of these ways are described in the next few sections.\nHaving access to the NODE_ENV is also useful for performing actions conditionally:\nWhen you compile the app with npm run build, the minification step will strip out this condition, and the resulting bundle will be smaller.\nReferencing Environment Variables in the HTML\nNote: this feature is available with react-scripts@0.9.0 and higher.\nYou can also access the environment variables starting with REACT_APP_ in the public/index.html. For example:\nNote that the caveats from the above section apply:\nAdding Temporary Environment Variables In Your Shell\nDefining environment variables can vary between OSes. It’s also important to know that this manner is temporary for the\nlife of the shell session.\n(Note: Quotes around the variable assignment are required to avoid a trailing whitespace.)\nAdding Development Environment Variables In .env\nNote: this feature is available with react-scripts@0.5.0 and higher.\nTo define permanent environment variables, create a file called .env in the root of your project:\nNote: 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. Changing any environment variables will require you to restart the development server if it is running.\n.env files should be checked into source control (with the exclusion of .env*.local).\nNote: this feature is available with react-scripts@1.0.0 and higher.\nFiles on the left have more priority than files on the right:\nThese variables will act as the defaults if the machine does not explicitly set them.\nPlease refer to the dotenv documentation for more details.\nNote: If you are defining environment variables for development, your CI and/or hosting platform will most likely need\nthese defined as well. Consult their documentation how to do this. For example, see the documentation for Travis CI or Heroku.\nNote: this feature is available with react-scripts@1.1.0 and higher.\nExpand variables already on your machine for use in your .env file (using dotenv-expand).\nFor example, to get the environment variable npm_package_version:\nOr expand variables local to the current .env file:\nCan I Use Decorators?\nMany popular libraries use decorators in their documentation.\nCreate React App doesn’t support decorator syntax at the moment because:\nHowever in many cases you can rewrite decorator-based code without decorators just as fine.\nPlease refer to these two threads for reference:\nCreate React App will add decorator support when the specification advances to a stable stage.\nFetching Data with AJAX Requests\nReact doesn't prescribe a specific approach to data fetching, but people commonly use either a library like axios or the fetch() API provided by the browser. Conveniently, Create React App includes a polyfill for fetch() so you can use it without worrying about the browser support.\nThe global fetch function allows to easily makes AJAX requests. It takes in a URL as an input and returns a Promise that resolves to a Response object. You can find more information about fetch here.\nThis project also includes a Promise polyfill which provides a full implementation of Promises/A+. A Promise represents the eventual result of an asynchronous operation, you can find more information about Promises here and here. Both axios and fetch() use Promises under the hood. You can also use the async / await syntax to reduce the callback nesting.\nYou can learn more about making AJAX requests from React components in the FAQ entry on the React website.\nIntegrating with an API Backend\nThese tutorials will help you to integrate your app with an API backend running on another port,\nusing fetch() to access it.\nNode\nCheck out this tutorial.\nYou can find the companion GitHub repository here.\nRuby on Rails\nCheck out this tutorial.\nYou can find the companion GitHub repository here.\nProxying API Requests in Development\nNote: this feature is available with react-scripts@0.2.3 and higher.\nPeople often serve the front-end React app from the same host and port as their backend implementation.\nFor example, a production setup might look like this after the app is deployed:\nSuch 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.\nTo 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:\nThis 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.\nConveniently, this avoids CORS issues and error messages like this in development:\nKeep 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.\nThe proxy option supports HTTP, HTTPS and WebSocket connections.\nIf the proxy option is not flexible enough for you, alternatively you can:\n\"Invalid Host Header\" Errors After Configuring Proxy\nWhen 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 and this issue.\nThis shouldn’t affect you when developing on localhost, but if you develop remotely like described here, you will see this error in the browser after enabling the proxy option:\nInvalid Host header\nTo work around it, you can specify your public development host in a file called .env.development in the root of your project:\nIf you restart the development server now and load the app from the specified host, it should work.\nIf 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:\nWe don’t recommend this approach.\nConfiguring the Proxy Manually\nNote: this feature is available with react-scripts@1.0.0 and higher.\nIf the proxy option is not flexible enough for you, you can specify an object in the following form (in package.json).\nYou may also specify any configuration value http-proxy-middleware or http-proxy supports.\nAll requests matching this path will be proxies, no exceptions. This includes requests for text/html, which the standard proxy option does not proxy.\nIf you need to specify multiple proxies, you may do so by specifying additional entries.\nMatches are regular expressions, so that you can use a regexp to match multiple paths.\nConfiguring a WebSocket Proxy\nWhen setting up a WebSocket proxy, there are a some extra considerations to be aware of.\nIf you’re using a WebSocket engine like 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.\nThere’s some good documentation available for setting up a Socket.io server.\nStandard WebSockets will work with a standard WebSocket server as well as the websocket.org echo test. You can use libraries like ws for the server, with native WebSockets in the browser.\nEither way, you can proxy WebSocket requests manually in package.json:\nUsing HTTPS in Development\nNote: this feature is available with react-scripts@0.4.0 and higher.\nYou may require the dev server to serve pages over HTTPS. One particular case where this could be useful is when using the \"proxy\" feature to proxy requests to an API server when that API server is itself serving HTTPS.\nTo do this, set the HTTPS environment variable to true, then start the dev server as usual with npm start:\n(Note: the lack of whitespace is intentional.)\nNote that the server will use a self-signed certificate, so your web browser will almost definitely display a warning upon accessing the page.\nGenerating Dynamic <meta> Tags on the Server\nSince Create React App doesn’t support server rendering, you might be wondering how to make <meta> tags dynamic and reflect the current URL. To solve this, we recommend to add placeholders into the HTML, like this:\nThen, 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!\nIf 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.\nPre-Rendering into Static HTML Files\nIf you’re hosting your build with a static hosting provider you can use react-snapshot or 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.\nThere are also opportunities to use this outside of static hosting, to take the pressure off the server when generating and caching routes.\nThe 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.\nYou can read more about zero-configuration pre-rendering (also called snapshotting) here.\nInjecting Data from the Server into the Page\nSimilarly to the previous section, you can leave some placeholders in the HTML that inject global variables, for example:\nThen, 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 as it makes your app vulnerable to XSS attacks.\nRunning Tests\nNote: this feature is available with react-scripts@0.3.0 and higher.\nRead the migration guide to learn how to enable it in older projects!\nCreate React App uses Jest as its test runner. To prepare for this integration, we did a major revamp of Jest so if you heard bad things about it years ago, give it another try.\nJest 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.\nWhile Jest provides browser globals such as window thanks to 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.\nWe 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.\nFilename Conventions\nJest will look for test files with any of the following popular naming conventions:\nThe .test.js / .spec.js files (or the __tests__ folders) can be located at any depth under the src top level folder.\nWe 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.\nCommand Line Interface\nWhen 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.\nThe 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:\n\nVersion Control Integration\nBy 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.\nJest 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.\nJest will always run all tests on a continuous integration server or if the project is not inside a Git or Mercurial repository.\nWriting Tests\nTo 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.\nJest provides a built-in expect() global function for making assertions. A basic test could look like this:\nAll expect() matchers supported by Jest are extensively documented here.\nYou can also use jest.fn() and expect(fn).toBeCalled() to create “spies” or mock functions.\nTesting Components\nThere 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.\nDifferent 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:\nThis test mounts a component and makes sure that it didn’t throw during rendering. Tests like this provide a lot of 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.\nWhen 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.\nIf you’d like to test components in isolation from the child components they render, we recommend using shallow() rendering API from Enzyme. To install it, run:\nAlternatively you may use yarn:\nAs 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.)\nThe adapter will also need to be configured in your global setup file:\nNote: Keep in mind that if you decide to \"eject\" before creating src/setupTests.js, the resulting package.json file won't contain any reference to it. Read here to learn how to add this after ejecting.\nNow you can write a smoke test with it:\nUnlike the previous smoke test using ReactDOM.render(), this test only renders <App> and doesn’t go deeper. For example, even if <App> itself renders a <Button> 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(), and you can also use it for testing state changes and component lifecycle.\nYou can read the Enzyme documentation 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.\nHere is an example from Enzyme documentation that asserts specific output, rewritten to use Jest matchers:\nAll Jest matchers are extensively documented here.\nNevertheless you can use a third-party assertion library like Chai if you want to, as described below.\nAdditionally, you might find jest-enzyme helpful to simplify your tests with readable matchers. The above contains code can be written more simply with jest-enzyme.\nTo enable this, install jest-enzyme:\nAlternatively you may use yarn:\nImport it in src/setupTests.js to make its matchers available in every test:\nUsing Third Party Assertion Libraries\nWe recommend that you use expect() for assertions and jest.fn() for spies. If you are having issues with them please file those against Jest, and we’ll fix them. We intend to keep making them better for React, supporting, for example, pretty-printing React elements as JSX.\nHowever, if you are used to other libraries, such as Chai and Sinon, or if you have existing code using them that you’d like to port over, you can import them normally like this:\nand then use them in your tests like you normally do.\nInitializing Test Environment\nNote: this feature is available with react-scripts@0.4.0 and higher.\nIf 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.\nFor example:\nNote: Keep in mind that if you decide to \"eject\" before creating src/setupTests.js, the resulting package.json file won't contain any reference to it, so you should manually create the property setupTestFrameworkScriptFile in the configuration for Jest, something like the following:\nFocusing and Excluding Tests\nYou can replace it() with xit() to temporarily exclude a test from being executed.\nSimilarly, fit() lets you focus on a specific test without running any other tests.\nCoverage Reporting\nJest has an integrated coverage reporter that works well with ES6 and requires no configuration.\nRun npm test -- --coverage (note extra -- in the middle) to include a coverage report like this:\n\nNote that tests run much slower with coverage so it is recommended to run it separately from your normal workflow.\nThe default Jest coverage configuration can be overriden by adding any of the following supported keys to a Jest config in your package.json.\nSupported overrides:\nExample package.json:\nContinuous Integration\nBy 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.\nWhen 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.\nPopular CI servers already set the environment variable CI by default but you can do this yourself too:\nOn CI servers\nFollow this article to set up CircleCI with a Create React App project.\nOn your own environment\n(Note: the lack of whitespace is intentional.)\nThe test command will force Jest to run tests once instead of launching the watcher.\nIf you find yourself doing this often in development, please file an issue 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.\nThe build command will check for linter warnings and fail if any are found.\nDisabling jsdom\nBy default, the package.json of the generated project looks like this:\nIf you know that none of your tests depend on jsdom, you can safely remove --env=jsdom, and your tests will run faster:\nTo help you make up your mind, here is a list of APIs that need jsdom:\nIn contrast, jsdom is not needed for the following APIs:\nFinally, jsdom is also not needed for snapshot testing.\nSnapshot Testing\nSnapshot 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.\nEditor Integration\nIf you use Visual Studio Code, there is a Jest extension 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.\n\nDebugging Tests\nThere are various ways to setup a debugger for your Jest tests. We cover debugging in Chrome and Visual Studio Code.\nNote: debugging tests requires Node 8 or higher.\nDebugging Tests in Chrome\nAdd the following to the scripts section in your project's package.json\nPlace debugger; statements in any test and run:\nThis will start running your Jest tests, but pause before executing to allow a debugger to attach to the process.\nOpen the following in Chrome\nAfter opening that link, the Chrome Developer Tools will be displayed. Select inspect on your process and a breakpoint will be set at the first line of the react script (this is done simply to give you time to open the developer tools and to prevent Jest from executing before you have time to do so). Click the button that looks like a \"play\" button in the upper right hand side of the screen to continue execution. When Jest executes the test that contains the debugger statement, execution will pause and you can examine the current scope and call stack.\nNote: the --runInBand cli option makes sure Jest runs test in the same process rather than spawning processes for individual tests. Normally Jest parallelizes test runs across processes but it is hard to debug many processes at the same time.\nDebugging Tests in Visual Studio Code\nDebugging Jest tests is supported out of the box for Visual Studio Code.\nUse the following launch.json configuration file:\nDeveloping Components in Isolation\nUsually, in an app, you have a lot of UI components, and each of them has many different states.\nFor an example, a simple button component could have following states:\nUsually, it’s hard to see these states without running a sample app or some examples.\nCreate React App doesn’t include any tools for this by default, but you can easily add Storybook for React (source) or React Styleguidist (source) to your project. These are third-party tools that let you develop components and see all their states in isolation from your app.\n\nYou 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.\nGetting Started with Storybook\nStorybook 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.\nFirst, install the following npm package globally:\nThen, run the following command inside your app’s directory:\nAfter that, follow the instructions on the screen.\nLearn more about React Storybook:\nGetting Started with Styleguidist\nStyleguidist 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.\nFirst, install Styleguidist:\nAlternatively you may use yarn:\nThen, add these scripts to your package.json:\nThen, run the following command inside your app’s directory:\nAfter that, follow the instructions on the screen.\nLearn more about React Styleguidist:\nPublishing Components to npm\nCreate React App doesn't provide any built-in functionality to publish a component to npm. If you're ready to extract a component from your project so other people can use it, we recommend moving it to a separate directory outside of your project and then using a tool like nwb to prepare it for publishing.\nMaking a Progressive Web App\nBy default, the production build is a fully functional, offline-first\nProgressive Web App.\nProgressive Web Apps are faster and more reliable than traditional web pages, and provide an engaging mobile experience:\nThe sw-precache-webpack-plugin\nis integrated into production configuration,\nand it will take care of generating a service worker file that will automatically\nprecache all of your local assets and keep them up to date as you deploy updates.\nThe service worker will use a cache-first strategy\nfor handling all requests for local assets, including the initial HTML, ensuring\nthat your web app is reliably fast, even on a slow or unreliable network.\nOpting Out of Caching\nIf you would prefer not to enable service workers prior to your initial\nproduction deployment, then remove the call to registerServiceWorker()\nfrom src/index.js.\nIf you had previously enabled service workers in your production deployment and\nhave decided that you would like to disable them for all your existing users,\nyou can swap out the call to registerServiceWorker() in\nsrc/index.js first by modifying the service worker import:\nand then call unregister() instead.\nAfter the user visits a page that has unregister(),\nthe service worker will be uninstalled. Note that depending on how /service-worker.js is served,\nit may take up to 24 hours for the cache to be invalidated.\nOffline-First Considerations\nService workers require HTTPS,\nalthough to facilitate local testing, that policy\ndoes not apply to localhost.\nIf your production web server does not support HTTPS, then the service worker\nregistration will fail, but the rest of your web app will remain functional.\nService workers are not currently supported\nin all web browsers. Service worker registration won't be attempted\non browsers that lack support.\nThe service worker is only enabled in the production environment,\ne.g. the output of npm run build. It's recommended that you do not enable an\noffline-first service worker in a development environment, as it can lead to\nfrustration when previously cached assets are used and do not include the latest\nchanges you've made locally.\nIf you need to test your offline-first service worker locally, build\nthe application (using npm run build) and run a simple http server from your\nbuild directory. After running the build script, create-react-app will give\ninstructions for one way to test your production build locally and the deployment instructions have\ninstructions for using other methods. Be sure to always use an\nincognito window to avoid complications with your browser cache.\nIf possible, configure your production environment to serve the generated\nservice-worker.js with HTTP caching disabled.\nIf that's not possible—GitHub Pages, for instance, does not\nallow you to change the default 10 minute HTTP cache lifetime—then be aware\nthat if you visit your production site, and then revisit again before\nservice-worker.js has expired from your HTTP cache, you'll continue to get\nthe previously cached assets from the service worker. If you have an immediate\nneed to view your updated production deployment, performing a shift-refresh\nwill temporarily disable the service worker and retrieve all assets from the\nnetwork.\nUsers aren't always familiar with offline-first web apps. It can be useful to\nlet the user know\nwhen the service worker has finished populating your caches (showing a \"This web\napp works offline!\" message) and also let them know when the service worker has\nfetched the latest updates that will be available the next time they load the\npage (showing a \"New content is available; please refresh.\" message). Showing\nthis messages is currently left as an exercise to the developer, but as a\nstarting point, you can make use of the logic included in src/registerServiceWorker.js, which\ndemonstrates which service worker lifecycle events to listen for to detect each\nscenario, and which as a default, just logs appropriate messages to the\nJavaScript console.\nBy default, the generated service worker file will not intercept or cache any\ncross-origin traffic, like HTTP API requests,\nimages, or embeds loaded from a different domain. If you would like to use a\nruntime caching strategy for those requests, you can eject\nand then configure the\nruntimeCaching\noption in the SWPrecacheWebpackPlugin section of\nwebpack.config.prod.js.\nProgressive Web App Metadata\nThe default configuration includes a web app manifest located at\npublic/manifest.json, that you can customize with\ndetails specific to your web application.\nWhen a user adds a web app to their homescreen using Chrome or Firefox on\nAndroid, the metadata in manifest.json determines what\nicons, names, and branding colors to use when the web app is displayed.\nThe Web App Manifest guide\nprovides more context about what each field means, and how your customizations\nwill affect your users' experience.\nAnalyzing the Bundle Size\nSource map explorer analyzes\nJavaScript bundles using the source maps. This helps you understand where code\nbloat is coming from.\nTo add Source map explorer to a Create React App project, follow these steps:\nAlternatively you may use yarn:\nThen in package.json, add the following line to scripts:\nThen to analyze the bundle run the production build then run the analyze\nscript.\nDeployment\nnpm run build creates a build directory with a production build of your app. Set up your favorite HTTP server so that a visitor to your site is served index.html, and requests to static paths like /static/js/main.<hash>.js are served with the contents of the /static/js/main.<hash>.js file.\nStatic Server\nFor environments using Node, the easiest way to handle this would be to install serve and let it handle the rest:\nThe last command shown above will serve your static site on the port 5000. Like many of serve’s internal settings, the port can be adjusted using the -p or --port flags.\nRun this command to get a full list of the options available:\nOther Solutions\nYou 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.\nHere’s a programmatic example using Node and Express:\nThe 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.\nThe build folder with static assets is the only output produced by Create React App.\nHowever 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.\nServing Apps with Client-Side Routing\nIf you use routers that use the HTML5 pushState history API under the hood (for example, 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.\nThis 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:\nIf you’re using Apache HTTP Server, you need to create a .htaccess file in the public folder that looks like this:\nIt will get copied to the build folder when you run npm run build.\nIf you’re using Apache Tomcat, you need to follow this Stack Overflow answer.\nNow requests to /todos/42 will be handled correctly both in development and in production.\nOn a production build, and in a browser that supports service workers,\nthe service worker will automatically handle all navigation requests, like for\n/todos/42, by serving the cached copy of your index.html. This\nservice worker navigation routing can be configured or disabled by\nejecting and then modifying the\nnavigateFallback\nand navigateFallbackWhitelist\noptions of the SWPreachePlugin configuration.\nWhen 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 and change start_url to match the required URL scheme, for example:\nBuilding for Relative Paths\nBy default, Create React App produces a build assuming your app is hosted at the server root.\nTo override this, specify the homepage in your package.json, for example:\nThis will let Create React App correctly infer the root path to use in the generated HTML file.\nNote: If you are using react-router@^4, you can root <Link>s using the basename prop on any <Router>.\nMore information here.\n\nFor example:\nNote: this feature is available with react-scripts@0.9.0 and higher.\nIf 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:\nThis 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.\nAzure\nSee this blog post on how to deploy your React app to Microsoft Azure.\nSee this blog post or this repo for a way to use automatic deployment to Azure App Service.\nFirebase\nInstall the Firebase CLI if you haven’t already by running npm install -g firebase-tools. Sign up for a Firebase account and create a new project. Run firebase login and login with your previous created Firebase account.\nThen 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.\nIMPORTANT: you need to set proper HTTP caching headers for service-worker.js file in firebase.json file or you will not be able to see changes after first deployment (issue #2440). It should be added inside \"hosting\" key like next:\nNow, after you create a production build with npm run build, you can deploy it by running firebase deploy.\nFor more information see Add Firebase to your JavaScript Project.\nGitHub Pages\nNote: this feature is available with react-scripts@0.2.0 and higher.\nThe step below is important!\nIf you skip it, your app will not deploy correctly.\nOpen your package.json and add a homepage field for your project:\nor for a GitHub user page:\nCreate React App uses the homepage field to determine the root URL in the built HTML file.\nNow, whenever you run npm run build, you will see a cheat sheet with instructions on how to deploy to GitHub Pages.\nTo publish it at https://myusername.github.io/my-app, run:\nAlternatively you may use yarn:\nAdd the following scripts in your package.json:\nThe predeploy script will run automatically before deploy is run.\nIf you are deploying to a GitHub user page instead of a project page you'll need to make two\nadditional modifications:\nThen run:\nFinally, make sure GitHub Pages option in your GitHub project settings is set to use the gh-pages branch:\n\nYou can configure a custom domain with GitHub Pages by adding a CNAME file to the public/ folder.\nGitHub 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:\nIf, when deploying, you get /dev/tty: No such a device or address or a similar error, try the follwing:\nHeroku\nUse the Heroku Buildpack for Create React App.\nYou can find instructions in Deploying React with Zero Configuration.\nSometimes npm run build works locally but fails during deploy via Heroku. Following are the most common cases.\nIf you get something like this:\nIt 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.\nThis 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.\nIf you exclude or ignore necessary files from the package you will see a error similar this one:\nIn this case, ensure that the file is there with the proper lettercase and that’s not ignored on your local .gitignore or ~/.gitignore_global.\nNetlify\nTo do a manual deploy to Netlify’s CDN:\nChoose build as the path to deploy.\nTo setup continuous delivery:\nWith this setup Netlify will build and deploy when you push to git or open a pull request:\nSupport for client-side routing:\nTo support pushState, make sure to create a public/_redirects file with the following rewrite rules:\nWhen you build the project, Create React App will place the public folder contents into the build output.\nNow\nNow offers a zero-configuration single-command deployment. You can use now to deploy your app for free.\nInstall the now command-line tool either via the recommended desktop tool or via node with npm install -g now.\nBuild your app by running npm run build.\nMove into the build directory by running cd build.\nRun now --name your-project-name from within the build directory. You will see a now.sh URL in your output like this:\nPaste that URL into your browser when the build is complete, and you will see your deployed app.\nDetails are available in this article.\nS3 and CloudFront\nSee this blog post on how to deploy your React app to Amazon Web Services S3 and CloudFront.\nSurge\nInstall 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.\nWhen asked about the project path, make sure to specify the build folder, for example:\nNote 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.\nAdvanced Configuration\nYou can adjust various development and production settings by setting environment variables in your shell or with .env.\nTroubleshooting\nnpm start doesn’t detect changes\nWhen you save a file while npm start is running, the browser should refresh with the updated code.\nIf this doesn’t happen, try one of the following workarounds:\nIf none of these solutions help please leave a comment in this thread.\nnpm test hangs on macOS Sierra\nIf 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 installation as described in facebookincubator/create-react-app#713.\nWe 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:\nIt is reported that installing Watchman 4.7.0 or newer fixes the issue. If you use Homebrew, you can run these commands to update it:\nYou can find other installation methods on the Watchman documentation page.\nIf this still doesn’t help, try running launchctl unload -F ~/Library/LaunchAgents/com.github.facebook.watchman.plist.\nThere are also reports that uninstalling Watchman fixes the issue. So if nothing else helps, remove it from your system and try again.\nnpm run build exits too early\nIt 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:\nThe 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.\nIf you are completely sure that you didn't terminate the process, consider adding some swap space to the machine you’re building on, or build the project locally.\nnpm run build fails on Heroku\nThis may be a problem with case sensitive filenames.\nPlease refer to this section.\nMoment.js locales are missing\nIf you use a Moment.js, 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.\nTo add a specific Moment.js locale to your bundle, you need to import it explicitly.\nFor example:\nIf import multiple locales this way, you can later switch between them by calling moment.locale() with the locale name:\nThis will only work for locales that have been explicitly imported before.\nnpm run build fails to minify\nSome 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.\nFork the package and publish a corrected version yourself.\nIf the dependency is small enough, copy it to your src/ folder and treat it as application code.\nIn 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.\nAlternatives to Ejecting\nEjecting lets you customize anything, but from that point on you have to maintain the configuration and scripts yourself. This can be daunting if you have many similar projects. In such cases instead of ejecting we recommend to fork react-scripts and any other packages you need. This article dives into how to do it in depth. You can find more discussion in this issue.\nSomething Missing?\nIf you have ideas for more “How To” recipes that should be on this page, let us know or contribute some!\nAbout\n\n An attempt to make a channel manager for Vacation Rentals\n \nResources\nStars\nWatchers\nForks\n\n\n Releases\n\n\n\n Packages\n 0\n\nLanguages\nFooter\nFooter navigation\n"}],"response

{"query":"channel manager made with react for hotels github","follow_up_questions":null,"answer":null,"images":["https://happyhotel.uk/wp-content/uploads/2021/06/EN_Channel-Manager-1024x576.jpg","https://www.hotelogix.com/images/distribution-channel-manager-top-banner-new.png","https://www.innroad.com/wp-content/uploads/2022/05/Channel-Manager-OTAs-1024x1024.png","https://www.erevmax.com/blog/wp-content/uploads/2019/07/erevmax-01-1.jpg","https://d2hbvxi6ld0iqf.cloudfront.net/Theme/img/channel-manager01.jpg"],"results":[{"title":"channel-manager · GitHub Topics · GitHub","url":"https://github.com/topics/channel-manager","content":"To associate your repository with the channel-manager topic, visit your repo's landing page and select \"manage topics.\" GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.","score":0.93663365,"raw_content":"Navigation Menu\nSearch code, repositories, users, issues, pull requests...\n\n Provide feedback\n \nWe read every piece of feedback, and take your input very seriously.\n\n Saved searches\n \nUse saved searches to filter your results more quickly\n\n To see all available qualifiers, see our documentation.\n \n\n channel-manager\n \n\n Here are\n 12 public repositories\n matching this topic...\n \n\n\n minical\n /\n \n minical\n \nMinical is an open-source PMS with extension management baked-in. It's designed for the companies looking for highly customizable property management software.\n\n\n openbroadcaster\n /\n \n observer\n \n 📻 OBServer Automation, Scheduler, Media Library and Player Manager\n\n\n openbroadcaster\n /\n \n obplayer\n \n 📻 OBPlayer Streaming Automation Playout with CAP EAS Alerting \n\n\n yilylong\n /\n \n ChannelTagView\n \n一个新闻频道管理view\n\n\n DrBookings\n /\n \n drbookings\n \nBooking managment through a rich graphical interface.\n\n\n tgMember\n /\n \n tgAttach\n \n\n\n sergree\n /\n \n samwell\n \nНебольшой Discord бот для нашего приватного сообщества\n\n\n minical\n /\n \n channex-integration\n \nThis extension helps integrate miniCal with Channex to connect to OTA's like Booking, Airbnb, and Expedia.\n\n\n openbroadcaster\n /\n \n status\n \n Shows server uptime, load, S.M.A.R.T status, and backup status\n\n\n GameFrameX\n /\n \n com.gameframex.unity.getchannel\n \n渠道获取\n\n\n tundradawn\n /\n \n audio-context-router\n \n🎧 Simple multi-channel audio playback, routing, and manipulation with Web Audio.\n\n\n hghhgh\n /\n \n TelegramChannelFiller\n \nA Simple Persian Channel Filler for Telegram channels in Python\n\n Improve this page\n \n\n Add a description, image, and links to the\n channel-manager\n topic page so that developers can more easily learn about it.\n \n\n\n Curate this topic\n \n\n\n\n\n\n Add this topic to your repo\n \n\n To associate your repository with the\n channel-manager\n topic, visit your repo's landing page and select \"manage topics.\"\n \n\n\n Learn more\n \n\n\n\n\nFooter\nFooter navigation\n"},{"title":"hotel-management-system · GitHub Topics · GitHub","url":"https://github.com/topics/hotel-management-system?l=javascript","content":"Simple hotel booking app with content management system. Users can book rooms in different hotels for specific dates. Hotel managers can create, update, delete a hotel and its rooms. Admin can manage everything in the app. graphql node mongodb reactjs webapp fullstack express-js hotel-management-system. Updated on Apr 19.","score":0.7895584,"raw_content":"Navigation Menu\nSearch code, repositories, users, issues, pull requests...\n\n Provide feedback\n \nWe read every piece of feedback, and take your input very seriously.\n\n Saved searches\n \nUse saved searches to filter your results more quickly\n\n To see all available qualifiers, see our documentation.\n \n\n hotel-management-system\n \n\n Here are\n 47 public repositories\n matching this topic...\n \n\n\n kimmyxpow\n /\n \n hollux\n \nHollux is a hotel website that can be used for online reservations.\n\n\n ayan-biswas0412\n /\n \n gssoc2021-HotelOnTouch\n \n👨‍🔧👨‍🔧Manage your all hotel services at one place - This is the project repository for HotelOnTouch Project and this project is actively looking for new contributors👨‍🔧👩‍🏫\n\n\n DebjitPramanick\n /\n \n Hotel-Booking-Web-App\n \nSimple hotel booking app with content management system. Users can book rooms in different hotels for specific dates. Hotel managers can create, update, delete a hotel and its rooms. Admin can manage everything in the app.\n\n\n Nabia-Sheikh\n /\n \n hotel-management-admin\n \nAdmin panel of Hotel management system with Firebase Realtime Database Integration.\n\n\n Darshan4114\n /\n \n django-hotel-management-system\n \nA Hotel Management System built with Django. I wrote 10 blogs and recorded 10 corresponding tutorial videos (youtube) on building this hotel management system.\n\n\n skmirajulislam\n /\n \n JourneyCusine\n \nMENR HOTEL BOOKING APPLICATION\n\n\n CodePapa360\n /\n \n The-Wild-Oasis\n \nHotel management app - full-featured React web application that allows hotel employees to manage cabins, bookings, and guests.\n\n\n Nabia-Sheikh\n /\n \n hotel-management-system\n \nHotel Management system with Firebase database & authentication. Dashboard included.\n\n\n itsteatv\n /\n \n itsteatv-hotel\n \nitsteatv-hotel\n\n\n eliudm\n /\n \n Food-order-and-table-reservation-system-\n \nit enables the user to order food online and also for a table reservation for dine-in if not delivery option.\n\n\n codx-ak\n /\n \n Restaurant-Management-System\n \nCreating a dynamic restaurant website using React, offering an interactive menu, online reservations, and reviews integration.\n\n\n kriti-raj\n /\n \n Hotel-Scaler\n \nScaler Assignment of Hotel Room Management Admin App\n\n\n patrickgratao\n /\n \n mykonos-hotel-management\n \nMykonos é um sistema para gerenciamento de hotéis, pousadas, hostels. Com ele você pode personalizar o atendimento aos seus hóspedes e criar uma experiência incrível para eles. \n\n\n mustafa-khaled\n /\n \n Hotel-Dashboard\n \nhotel management System using React and Supabase\n\n\n duongviet2904\n /\n \n hotel-management-system-php\n \nHotel management website using PHP, MySQL\n\n\n ValdesChe\n /\n \n Revolution_hotel\n \nA web application for hotel management developped using Playframework ( JAVA ) , Scala , JS , HTML and CSS. \n\n\n ritiksharmarj\n /\n \n oasisresort\n \nAn internal hotel management system allows employees to manage everything about hotel bookings, cabins, and guests.\n\n\n awaismohammad23\n /\n \n React-Login-Page-Test\n \nThis repo contains a login page and implementation of the list of hotels that have been listed using cards.\n\n\n ibrahim11elian\n /\n \n hotel-dashboard\n \nA web application that allows you to manage your hotel. from managing cabins to bookings and check-in and out.\n\n\n daoson12\n /\n \n Hotel-Booking-app\n \nThe project hotel booking app is a web-based application that allows the hotel manager and guests/users to handle all hotel activities online. \n\n Improve this page\n \n\n Add a description, image, and links to the\n hotel-management-system\n topic page so that developers can more easily learn about it.\n \n\n\n Curate this topic\n \n\n\n\n\n\n Add this topic to your repo\n \n\n To associate your repository with the\n hotel-management-system\n topic, visit your repo's landing page and select \"manage topics.\"\n \n\n\n Learn more\n \n\n\n\n\nFooter\nFooter navigation\n"},{"title":"v-vigraman/hotel_channel_manager | GitHub","url":"https://github.com/v-vigraman/hotel_channel_manager","content":"You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window.","score":0.009522486,"raw_content":"Navigation Menu\nSearch code, repositories, users, issues, pull requests...\n\n Provide feedback\n \nWe read every piece of feedback, and take your input very seriously.\n\n Saved searches\n \nUse saved searches to filter your results more quickly\n\n To see all available qualifiers, see our documentation.\n \nv-vigraman/hotel_channel_manager\nFolders and files\nLatest commit\nHistory\nRepository files navigation\nThis project was bootstrapped with Create React App.\nAvailable Scripts\nIn the project directory, you can run:\nnpm start\nRuns the app in the development mode.\nOpen http://localhost:3000 to view it in the browser.\nThe page will reload if you make edits.\nYou will also see any lint errors in the console.\nnpm test\nLaunches the test runner in the interactive watch mode.\nSee the section about running tests for more information.\nnpm run build\nBuilds the app for production to the build folder.\nIt correctly bundles React in production mode and optimizes the build for the best performance.\nThe build is minified and the filenames include the hashes.\nYour app is ready to be deployed!\nSee the section about deployment for more information.\nnpm run eject\nNote: this is a one-way operation. Once you eject, you can’t go back!\nIf 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.\nInstead, 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.\nYou 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.\nLearn More\nYou can learn more in the Create React App documentation.\nTo learn React, check out the React documentation.\nCode Splitting\nThis section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting\nAnalyzing the Bundle Size\nThis section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size\nMaking a Progressive Web App\nThis section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app\nAdvanced Configuration\nThis section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration\nDeployment\nThis section has moved here: https://facebook.github.io/create-react-app/docs/deployment\nnpm run build fails to minify\nThis section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify\nAbout\nResources\nStars\nWatchers\nForks\n\n\n Releases\n\n\n\n Packages\n 0\n\nLanguages\nFooter\nFooter navigation\n"},{"title":"RAJUVHAI/Hotel-management-react-js: Hotel management system | GitHub","url":"https://github.com/RAJUVHAI/Hotel-management-react-js","content":"npm run build. Builds the app for production to the build folder. It correctly bundles React in production mode and optimizes the build for the best performance. The build is minified and the filenames include the hashes. Your app is ready to be deployed!","score":0.00498227,"raw_content":"Navigation Menu\nSearch code, repositories, users, issues, pull requests...\n\n Provide feedback\n \nWe read every piece of feedback, and take your input very seriously.\n\n Saved searches\n \nUse saved searches to filter your results more quickly\n\n To see all available qualifiers, see our documentation.\n \n\n Hotel management system \n \nRAJUVHAI/Hotel-management-react-js\nFolders and files\nLatest commit\nHistory\nRepository files navigation\nGetting Started with Create React App\nThis project was bootstrapped with Create React App.\nAvailable Scripts\nIn the project directory, you can run:\nnpm start\nRuns the app in the development mode.\nOpen http://localhost:3000 to view it in your browser.\nThe page will reload when you make changes.\nYou may also see any lint errors in the console.\nnpm test\nLaunches the test runner in the interactive watch mode.\nSee the section about running tests for more information.\nnpm run build\nBuilds the app for production to the build folder.\nIt correctly bundles React in production mode and optimizes the build for the best performance.\nThe build is minified and the filenames include the hashes.\nYour app is ready to be deployed!\nSee the section about deployment for more information.\nnpm run eject\nNote: this is a one-way operation. Once you eject, you can't go back!\nIf 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.\nInstead, 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.\nYou 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.\nLearn More\nYou can learn more in the Create React App documentation.\nTo learn React, check out the React documentation.\nCode Splitting\nThis section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting\nAnalyzing the Bundle Size\nThis section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size\nMaking a Progressive Web App\nThis section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app\nAdvanced Configuration\nThis section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration\nDeployment\nThis section has moved here: https://facebook.github.io/create-react-app/docs/deployment\nnpm run build fails to minify\nThis section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify\nAbout\n\n Hotel management system \n \nTopics\nResources\nStars\nWatchers\nForks\n\n\n Releases\n\n\n\n Packages\n 0\n\nLanguages\nFooter\nFooter navigation\n"},{"title":"GitHub | mavarazy/channel-manager: An attempt to make a channel manager ...","url":"https://github.com/mavarazy/channel-manager","content":"Create React App is divided into two packages: create-react-app is a global command-line utility that you use to create new projects.; react-scripts is a development dependency in the generated projects (including this one).; You almost never need to update create-react-app itself: it delegates all the setup to react-scripts.. When you run create-react-app, it always creates the project with ...","score":0.0013198635,"raw_content":"Navigation Menu\nSearch code, repositories, users, issues, pull requests...\n\n Provide feedback\n \nWe read every piece of feedback, and take your input very seriously.\n\n Saved searches\n \nUse saved searches to filter your results more quickly\n\n To see all available qualifiers, see our documentation.\n \n\n An attempt to make a channel manager for Vacation Rentals\n \nmavarazy/channel-manager\nFolders and files\nLatest commit\nHistory\nRepository files navigation\nThis project was bootstrapped with Create React App.\nBelow you will find some information on how to perform common tasks.\nYou can find the most recent version of this guide here.\nTable of Contents\nUpdating to New Releases\nCreate React App is divided into two packages:\nYou almost never need to update create-react-app itself: it delegates all the setup to react-scripts.\nWhen 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.\nTo update an existing project to a new version of react-scripts, open the changelog, 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.\nIn 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 for potential breaking changes.\nWe commit to keeping the breaking changes minimal so you can upgrade react-scripts painlessly.\nSending Feedback\nWe are always open to your feedback.\nFolder Structure\nAfter creation, your project should look like this:\nFor the project to build, these files must exist with exact filenames:\nYou can delete or rename the other files.\nYou may create subdirectories inside src. For faster rebuilds, only files inside src are processed by Webpack.\nYou need to put any JS and CSS files inside src, otherwise Webpack won’t see them.\nOnly files inside public can be used from public/index.html.\nRead instructions below for using assets from JavaScript and HTML.\nYou can, however, create more top-level directories.\nThey will not be included in the production build so you can use them for things like documentation.\nAvailable Scripts\nIn the project directory, you can run:\nnpm start\nRuns the app in the development mode.\nOpen http://localhost:3000 to view it in the browser.\nThe page will reload if you make edits.\nYou will also see any lint errors in the console.\nnpm test\nLaunches the test runner in the interactive watch mode.\nSee the section about running tests for more information.\nnpm run build\nBuilds the app for production to the build folder.\nIt correctly bundles React in production mode and optimizes the build for the best performance.\nThe build is minified and the filenames include the hashes.\nYour app is ready to be deployed!\nSee the section about deployment for more information.\nnpm run eject\nNote: this is a one-way operation. Once you eject, you can’t go back!\nIf 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.\nInstead, 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.\nYou 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.\nSupported Browsers\nBy default, the generated project uses the latest version of React.\nYou can refer to the React documentation for more information about supported browsers.\nSupported Language Features and Polyfills\nThis project supports a superset of the latest JavaScript standard.\nIn addition to ES6 syntax features, it also supports:\nLearn more about different proposal stages.\nWhile we recommend using experimental proposals with some caution, Facebook heavily uses these features in the product code, so we intend to provide codemods if any of these proposals change in the future.\nNote that the project only includes a few ES6 polyfills:\nIf 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.\nAlso note that using some newer syntax features like for...of or [...nonArrayValue] causes Babel to emit code that depends on ES6 runtime features and might not work without a polyfill. When in doubt, use Babel REPL to see what any specific syntax compiles down to.\nSyntax Highlighting in the Editor\nTo configure the syntax highlighting in your favorite text editor, head to the relevant Babel documentation page and follow the instructions. Some of the most popular editors are covered.\nDisplaying Lint Output in the Editor\nNote: this feature is available with react-scripts@0.2.0 and higher.\nIt also only works with npm 3 or higher.\nSome editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint.\nThey 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.\nYou would need to install an ESLint plugin for your editor first. Then, add a file called .eslintrc to the project root:\nNow your editor should report the linting warnings.\nNote 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.\nIf you want to enforce a coding style for your project, consider using Prettier instead of ESLint style rules.\nDebugging in the Editor\nThis feature is currently only supported by Visual Studio Code and WebStorm.\nVisual 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.\nVisual Studio Code\nYou would need to have the latest version of VS Code and VS Code Chrome Debugger Extension installed.\nThen add the block below to your launch.json file and put it inside the .vscode folder in your app’s root directory.\nNote: the URL may be different if you've made adjustments via the HOST or PORT environment variables.\nStart 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.\nHaving problems with VS Code Debugging? Please see their troubleshooting guide.\nWebStorm\nYou would need to have WebStorm and JetBrains IDE Support Chrome extension installed.\nIn 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.\nNote: the URL may be different if you've made adjustments via the HOST or PORT environment variables.\nStart 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.\nThe same way you can debug your application in IntelliJ IDEA Ultimate, PhpStorm, PyCharm Pro, and RubyMine.\nFormatting Code Automatically\nPrettier 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 for more information, and look at this page to see it in action.\nTo format our code whenever we make a commit in git, we need to install the following dependencies:\nAlternatively you may use yarn:\nNow we can make sure every file is formatted correctly by adding a few lines to the package.json in the project root.\nAdd the following line to scripts section:\nNext we add a 'lint-staged' field to the package.json, for example:\nNow, 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,json,css}\" to format your entire project for the first time.\nNext you might want to integrate Prettier in your favorite editor. Read the section on Editor Integration on the Prettier GitHub page.\nChanging the Page \nYou 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.\nNote that normally you wouldn’t edit files in the public folder very often. For example, adding a stylesheet is done without touching the HTML.\nIf you need to dynamically update the page title based on the content, you can use the browser document.title API. For more complex scenarios when you want to change the title from React components, you can use React Helmet, a third party library.\nIf 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. Alternatively, you can pre-build each page as a static HTML file which then loads the JavaScript bundle, which is covered here.\nInstalling a Dependency\nThe 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:\nAlternatively you may use yarn:\nThis works for any library, not just react-router.\nImporting a Component\nThis project setup supports ES6 modules thanks to Babel.\nWhile you can still use require() and module.exports, we encourage you to use import and export instead.\nFor example:\nButton.js\nDangerButton.js\nBe aware of the difference between default and named exports. It is a common source of mistakes.\nWe 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'.\nNamed 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.\nLearn more about ES6 modules:\nCode Splitting\nInstead 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.\nThis project setup supports code splitting via dynamic import(). Its proposal is in stage 3. The import() function-like form takes the module name as an argument and returns a Promise which always resolves to the namespace object of the module.\nHere is an example:\nmoduleA.js\nApp.js\nThis will make moduleA.js and all its unique dependencies as a separate chunk that only loads after the user clicks the 'Load' button.\nYou can also use it with async / await syntax if you prefer it.\nWith React Router\nIf you are using React Router check out this tutorial on how to use code splitting with it. You can find the companion GitHub repository here.\nAlso check out the Code Splitting section in React documentation.\nAdding a Stylesheet\nThis project setup uses Webpack 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:\nButton.css\nButton.js\nThis is not required for React but many people find this feature convenient. You can read about the benefits of this approach here. However you should be aware that this makes your code less portable to other build tools and environments than Webpack.\nIn 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.\nIf 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.\nPost-Processing CSS\nThis project setup minifies your CSS and adds vendor prefixes to it automatically through Autoprefixer so you don’t need to worry about it.\nFor example, this:\nbecomes this:\nIf you need to disable autoprefixing for some reason, follow this section.\nAdding a CSS Preprocessor (Sass, Less etc.)\nGenerally, 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).\nFollowing 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.\nFirst, let’s install the command-line interface for Sass:\nAlternatively you may use yarn:\nThen in package.json, add the following lines to scripts:\nNote: To use a different preprocessor, replace build-css and watch-css commands according to your preprocessor’s documentation.\nNow 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.\nTo 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.\nTo enable importing files without using relative paths, you can add the --include-path option to the command in package.json.\nThis will allow you to do imports like\nAt 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.\nAs 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:\nAlternatively you may use yarn:\nThen we can change start and build scripts to include the CSS preprocessor commands:\nNow running npm start and npm run build also builds Sass files.\nWhy node-sass-chokidar?\nnode-sass has been reported as having the following issues:\nnode-sass --watch has been reported to have performance issues in certain conditions when used in a virtual machine or with docker.\nInfinite styles compiling #1939\nnode-sass has been reported as having issues with detecting new files in a directory #1891\nnode-sass-chokidar is used here as it addresses these issues.\nAdding Images, Fonts, and Files\nWith Webpack, using static assets like images and fonts works similarly to CSS.\nYou 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.\nTo reduce the number of requests to the server, importing images that are less than 10,000 bytes returns a data URI instead of a path. This applies to the following file extensions: bmp, gif, jpg, jpeg, and png. SVG files are excluded due to #1153.\nHere is an example:\nThis ensures that when the project is built, Webpack will correctly move the images into the build folder, and provide us with correct paths.\nThis works in CSS too:\nWebpack 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.\nPlease be advised that this is also a custom feature of Webpack.\nIt is not required for React but many people enjoy it (and React Native uses a similar mechanism for images).\nAn alternative way of handling static assets is described in the next section.\nUsing the public Folder\nNote: this feature is available with react-scripts@0.5.0 and higher.\nChanging the HTML\nThe public folder contains the HTML file so you can tweak it, for example, to set the page title.\nThe <script> tag with the compiled code will be added to it automatically during the build process.\nAdding Assets Outside of the Module System\nYou can also add other assets to the public folder.\nNote that we normally encourage you to import assets in JavaScript files instead.\nFor example, see the sections on adding a stylesheet and adding images and fonts.\nThis mechanism provides a number of benefits:\nHowever there is an escape hatch that you can use to add an asset outside of the module system.\nIf 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.\nInside index.html, you can use it like this:\nOnly 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.\nWhen 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.\nIn JavaScript code, you can use process.env.PUBLIC_URL for similar purposes:\nKeep in mind the downsides of this approach:\nWhen to Use the public Folder\nNormally we recommend importing stylesheets, images, and fonts from JavaScript.\nThe public folder is useful as a workaround for a number of less common cases:\nNote that if you add a <script> that declares global variables, you also need to read the next section on using them.\nUsing Global Variables\nWhen 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.\nYou can avoid this by reading the global variable explicitly from the window object, for example:\nThis makes it obvious you are using a global variable intentionally rather than because of a typo.\nAlternatively, you can force the linter to ignore any line by adding // eslint-disable-line after it.\nAdding Bootstrap\nYou don’t have to use React Bootstrap 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:\nInstall React Bootstrap and Bootstrap from npm. React Bootstrap does not include Bootstrap CSS so this needs to be installed as well:\nAlternatively you may use yarn:\nImport Bootstrap CSS and optionally Bootstrap theme CSS in the beginning of your src/index.js file:\nImport required React Bootstrap components within src/App.js file or your custom component files:\nNow 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 redone using React Bootstrap.\nUsing a Custom Theme\nSometimes you might need to tweak the visual styles of Bootstrap (or equivalent package).\nWe suggest the following approach:\nHere is an example of adding a customized Bootstrap that follows these steps.\nAdding Flow\nFlow is a static type checker that helps you write code with fewer bugs. Check out this introduction to using static types in JavaScript if you are new to this concept.\nRecent versions of Flow work with Create React App projects out of the box.\nTo add Flow to a Create React App project, follow these steps:\nNow you can run npm run flow (or yarn flow) to check the files for type errors.\nYou can optionally use an IDE like Nuclide for a better integrated experience.\nIn the future we plan to integrate it into Create React App even more closely.\nTo learn more about Flow, check out its documentation.\nAdding a Router\nCreate React App doesn't prescribe a specific routing solution, but React Router is the most popular one.\nTo add it, run:\nAlternatively you may use yarn:\nTo try it, delete all the code in src/App.js and replace it with any of the examples on its website. The Basic Example is a good place to get started.\nNote that you may need to configure your production server to support client-side routing before deploying your app.\nAdding Custom Environment Variables\nNote: this feature is available with react-scripts@0.2.3 and higher.\nYour project can consume variables declared in your environment as if they were declared locally in your JS files. By\ndefault you will have NODE_ENV defined for you, and any other environment variables starting with\nREACT_APP_.\nThe 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. Alternatively you can rebuild the app on the server anytime you change them.\nNote: 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. Changing any environment variables will require you to restart the development server if it is running.\nThese environment variables will be defined for you on process.env. For example, having an environment\nvariable named REACT_APP_SECRET_CODE will be exposed in your JS as process.env.REACT_APP_SECRET_CODE.\nThere 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.\nThese environment variables can be useful for displaying information conditionally based on where the project is\ndeployed or consuming sensitive data that lives outside of version control.\nFirst, you need to have environment variables defined. For example, let’s say you wanted to consume a secret defined\nin the environment inside a <form>:\nDuring 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.\nWhen 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:\nThe above form is looking for a variable called REACT_APP_SECRET_CODE from the environment. In order to consume this\nvalue, we need to have it defined in the environment. This can be done using two ways: either in your shell or in\na .env file. Both of these ways are described in the next few sections.\nHaving access to the NODE_ENV is also useful for performing actions conditionally:\nWhen you compile the app with npm run build, the minification step will strip out this condition, and the resulting bundle will be smaller.\nReferencing Environment Variables in the HTML\nNote: this feature is available with react-scripts@0.9.0 and higher.\nYou can also access the environment variables starting with REACT_APP_ in the public/index.html. For example:\nNote that the caveats from the above section apply:\nAdding Temporary Environment Variables In Your Shell\nDefining environment variables can vary between OSes. It’s also important to know that this manner is temporary for the\nlife of the shell session.\n(Note: Quotes around the variable assignment are required to avoid a trailing whitespace.)\nAdding Development Environment Variables In .env\nNote: this feature is available with react-scripts@0.5.0 and higher.\nTo define permanent environment variables, create a file called .env in the root of your project:\nNote: 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. Changing any environment variables will require you to restart the development server if it is running.\n.env files should be checked into source control (with the exclusion of .env*.local).\nNote: this feature is available with react-scripts@1.0.0 and higher.\nFiles on the left have more priority than files on the right:\nThese variables will act as the defaults if the machine does not explicitly set them.\nPlease refer to the dotenv documentation for more details.\nNote: If you are defining environment variables for development, your CI and/or hosting platform will most likely need\nthese defined as well. Consult their documentation how to do this. For example, see the documentation for Travis CI or Heroku.\nNote: this feature is available with react-scripts@1.1.0 and higher.\nExpand variables already on your machine for use in your .env file (using dotenv-expand).\nFor example, to get the environment variable npm_package_version:\nOr expand variables local to the current .env file:\nCan I Use Decorators?\nMany popular libraries use decorators in their documentation.\nCreate React App doesn’t support decorator syntax at the moment because:\nHowever in many cases you can rewrite decorator-based code without decorators just as fine.\nPlease refer to these two threads for reference:\nCreate React App will add decorator support when the specification advances to a stable stage.\nFetching Data with AJAX Requests\nReact doesn't prescribe a specific approach to data fetching, but people commonly use either a library like axios or the fetch() API provided by the browser. Conveniently, Create React App includes a polyfill for fetch() so you can use it without worrying about the browser support.\nThe global fetch function allows to easily makes AJAX requests. It takes in a URL as an input and returns a Promise that resolves to a Response object. You can find more information about fetch here.\nThis project also includes a Promise polyfill which provides a full implementation of Promises/A+. A Promise represents the eventual result of an asynchronous operation, you can find more information about Promises here and here. Both axios and fetch() use Promises under the hood. You can also use the async / await syntax to reduce the callback nesting.\nYou can learn more about making AJAX requests from React components in the FAQ entry on the React website.\nIntegrating with an API Backend\nThese tutorials will help you to integrate your app with an API backend running on another port,\nusing fetch() to access it.\nNode\nCheck out this tutorial.\nYou can find the companion GitHub repository here.\nRuby on Rails\nCheck out this tutorial.\nYou can find the companion GitHub repository here.\nProxying API Requests in Development\nNote: this feature is available with react-scripts@0.2.3 and higher.\nPeople often serve the front-end React app from the same host and port as their backend implementation.\nFor example, a production setup might look like this after the app is deployed:\nSuch 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.\nTo 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:\nThis 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.\nConveniently, this avoids CORS issues and error messages like this in development:\nKeep 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.\nThe proxy option supports HTTP, HTTPS and WebSocket connections.\nIf the proxy option is not flexible enough for you, alternatively you can:\n\"Invalid Host Header\" Errors After Configuring Proxy\nWhen 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 and this issue.\nThis shouldn’t affect you when developing on localhost, but if you develop remotely like described here, you will see this error in the browser after enabling the proxy option:\nInvalid Host header\nTo work around it, you can specify your public development host in a file called .env.development in the root of your project:\nIf you restart the development server now and load the app from the specified host, it should work.\nIf 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:\nWe don’t recommend this approach.\nConfiguring the Proxy Manually\nNote: this feature is available with react-scripts@1.0.0 and higher.\nIf the proxy option is not flexible enough for you, you can specify an object in the following form (in package.json).\nYou may also specify any configuration value http-proxy-middleware or http-proxy supports.\nAll requests matching this path will be proxies, no exceptions. This includes requests for text/html, which the standard proxy option does not proxy.\nIf you need to specify multiple proxies, you may do so by specifying additional entries.\nMatches are regular expressions, so that you can use a regexp to match multiple paths.\nConfiguring a WebSocket Proxy\nWhen setting up a WebSocket proxy, there are a some extra considerations to be aware of.\nIf you’re using a WebSocket engine like 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.\nThere’s some good documentation available for setting up a Socket.io server.\nStandard WebSockets will work with a standard WebSocket server as well as the websocket.org echo test. You can use libraries like ws for the server, with native WebSockets in the browser.\nEither way, you can proxy WebSocket requests manually in package.json:\nUsing HTTPS in Development\nNote: this feature is available with react-scripts@0.4.0 and higher.\nYou may require the dev server to serve pages over HTTPS. One particular case where this could be useful is when using the \"proxy\" feature to proxy requests to an API server when that API server is itself serving HTTPS.\nTo do this, set the HTTPS environment variable to true, then start the dev server as usual with npm start:\n(Note: the lack of whitespace is intentional.)\nNote that the server will use a self-signed certificate, so your web browser will almost definitely display a warning upon accessing the page.\nGenerating Dynamic <meta> Tags on the Server\nSince Create React App doesn’t support server rendering, you might be wondering how to make <meta> tags dynamic and reflect the current URL. To solve this, we recommend to add placeholders into the HTML, like this:\nThen, 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!\nIf 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.\nPre-Rendering into Static HTML Files\nIf you’re hosting your build with a static hosting provider you can use react-snapshot or 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.\nThere are also opportunities to use this outside of static hosting, to take the pressure off the server when generating and caching routes.\nThe 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.\nYou can read more about zero-configuration pre-rendering (also called snapshotting) here.\nInjecting Data from the Server into the Page\nSimilarly to the previous section, you can leave some placeholders in the HTML that inject global variables, for example:\nThen, 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 as it makes your app vulnerable to XSS attacks.\nRunning Tests\nNote: this feature is available with react-scripts@0.3.0 and higher.\nRead the migration guide to learn how to enable it in older projects!\nCreate React App uses Jest as its test runner. To prepare for this integration, we did a major revamp of Jest so if you heard bad things about it years ago, give it another try.\nJest 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.\nWhile Jest provides browser globals such as window thanks to 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.\nWe 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.\nFilename Conventions\nJest will look for test files with any of the following popular naming conventions:\nThe .test.js / .spec.js files (or the __tests__ folders) can be located at any depth under the src top level folder.\nWe 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.\nCommand Line Interface\nWhen 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.\nThe 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:\n\nVersion Control Integration\nBy 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.\nJest 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.\nJest will always run all tests on a continuous integration server or if the project is not inside a Git or Mercurial repository.\nWriting Tests\nTo 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.\nJest provides a built-in expect() global function for making assertions. A basic test could look like this:\nAll expect() matchers supported by Jest are extensively documented here.\nYou can also use jest.fn() and expect(fn).toBeCalled() to create “spies” or mock functions.\nTesting Components\nThere 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.\nDifferent 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:\nThis test mounts a component and makes sure that it didn’t throw during rendering. Tests like this provide a lot of 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.\nWhen 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.\nIf you’d like to test components in isolation from the child components they render, we recommend using shallow() rendering API from Enzyme. To install it, run:\nAlternatively you may use yarn:\nAs 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.)\nThe adapter will also need to be configured in your global setup file:\nNote: Keep in mind that if you decide to \"eject\" before creating src/setupTests.js, the resulting package.json file won't contain any reference to it. Read here to learn how to add this after ejecting.\nNow you can write a smoke test with it:\nUnlike the previous smoke test using ReactDOM.render(), this test only renders <App> and doesn’t go deeper. For example, even if <App> itself renders a <Button> 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(), and you can also use it for testing state changes and component lifecycle.\nYou can read the Enzyme documentation 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.\nHere is an example from Enzyme documentation that asserts specific output, rewritten to use Jest matchers:\nAll Jest matchers are extensively documented here.\nNevertheless you can use a third-party assertion library like Chai if you want to, as described below.\nAdditionally, you might find jest-enzyme helpful to simplify your tests with readable matchers. The above contains code can be written more simply with jest-enzyme.\nTo enable this, install jest-enzyme:\nAlternatively you may use yarn:\nImport it in src/setupTests.js to make its matchers available in every test:\nUsing Third Party Assertion Libraries\nWe recommend that you use expect() for assertions and jest.fn() for spies. If you are having issues with them please file those against Jest, and we’ll fix them. We intend to keep making them better for React, supporting, for example, pretty-printing React elements as JSX.\nHowever, if you are used to other libraries, such as Chai and Sinon, or if you have existing code using them that you’d like to port over, you can import them normally like this:\nand then use them in your tests like you normally do.\nInitializing Test Environment\nNote: this feature is available with react-scripts@0.4.0 and higher.\nIf 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.\nFor example:\nNote: Keep in mind that if you decide to \"eject\" before creating src/setupTests.js, the resulting package.json file won't contain any reference to it, so you should manually create the property setupTestFrameworkScriptFile in the configuration for Jest, something like the following:\nFocusing and Excluding Tests\nYou can replace it() with xit() to temporarily exclude a test from being executed.\nSimilarly, fit() lets you focus on a specific test without running any other tests.\nCoverage Reporting\nJest has an integrated coverage reporter that works well with ES6 and requires no configuration.\nRun npm test -- --coverage (note extra -- in the middle) to include a coverage report like this:\n\nNote that tests run much slower with coverage so it is recommended to run it separately from your normal workflow.\nThe default Jest coverage configuration can be overriden by adding any of the following supported keys to a Jest config in your package.json.\nSupported overrides:\nExample package.json:\nContinuous Integration\nBy 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.\nWhen 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.\nPopular CI servers already set the environment variable CI by default but you can do this yourself too:\nOn CI servers\nFollow this article to set up CircleCI with a Create React App project.\nOn your own environment\n(Note: the lack of whitespace is intentional.)\nThe test command will force Jest to run tests once instead of launching the watcher.\nIf you find yourself doing this often in development, please file an issue 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.\nThe build command will check for linter warnings and fail if any are found.\nDisabling jsdom\nBy default, the package.json of the generated project looks like this:\nIf you know that none of your tests depend on jsdom, you can safely remove --env=jsdom, and your tests will run faster:\nTo help you make up your mind, here is a list of APIs that need jsdom:\nIn contrast, jsdom is not needed for the following APIs:\nFinally, jsdom is also not needed for snapshot testing.\nSnapshot Testing\nSnapshot 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.\nEditor Integration\nIf you use Visual Studio Code, there is a Jest extension 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.\n\nDebugging Tests\nThere are various ways to setup a debugger for your Jest tests. We cover debugging in Chrome and Visual Studio Code.\nNote: debugging tests requires Node 8 or higher.\nDebugging Tests in Chrome\nAdd the following to the scripts section in your project's package.json\nPlace debugger; statements in any test and run:\nThis will start running your Jest tests, but pause before executing to allow a debugger to attach to the process.\nOpen the following in Chrome\nAfter opening that link, the Chrome Developer Tools will be displayed. Select inspect on your process and a breakpoint will be set at the first line of the react script (this is done simply to give you time to open the developer tools and to prevent Jest from executing before you have time to do so). Click the button that looks like a \"play\" button in the upper right hand side of the screen to continue execution. When Jest executes the test that contains the debugger statement, execution will pause and you can examine the current scope and call stack.\nNote: the --runInBand cli option makes sure Jest runs test in the same process rather than spawning processes for individual tests. Normally Jest parallelizes test runs across processes but it is hard to debug many processes at the same time.\nDebugging Tests in Visual Studio Code\nDebugging Jest tests is supported out of the box for Visual Studio Code.\nUse the following launch.json configuration file:\nDeveloping Components in Isolation\nUsually, in an app, you have a lot of UI components, and each of them has many different states.\nFor an example, a simple button component could have following states:\nUsually, it’s hard to see these states without running a sample app or some examples.\nCreate React App doesn’t include any tools for this by default, but you can easily add Storybook for React (source) or React Styleguidist (source) to your project. These are third-party tools that let you develop components and see all their states in isolation from your app.\n\nYou 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.\nGetting Started with Storybook\nStorybook 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.\nFirst, install the following npm package globally:\nThen, run the following command inside your app’s directory:\nAfter that, follow the instructions on the screen.\nLearn more about React Storybook:\nGetting Started with Styleguidist\nStyleguidist 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.\nFirst, install Styleguidist:\nAlternatively you may use yarn:\nThen, add these scripts to your package.json:\nThen, run the following command inside your app’s directory:\nAfter that, follow the instructions on the screen.\nLearn more about React Styleguidist:\nPublishing Components to npm\nCreate React App doesn't provide any built-in functionality to publish a component to npm. If you're ready to extract a component from your project so other people can use it, we recommend moving it to a separate directory outside of your project and then using a tool like nwb to prepare it for publishing.\nMaking a Progressive Web App\nBy default, the production build is a fully functional, offline-first\nProgressive Web App.\nProgressive Web Apps are faster and more reliable than traditional web pages, and provide an engaging mobile experience:\nThe sw-precache-webpack-plugin\nis integrated into production configuration,\nand it will take care of generating a service worker file that will automatically\nprecache all of your local assets and keep them up to date as you deploy updates.\nThe service worker will use a cache-first strategy\nfor handling all requests for local assets, including the initial HTML, ensuring\nthat your web app is reliably fast, even on a slow or unreliable network.\nOpting Out of Caching\nIf you would prefer not to enable service workers prior to your initial\nproduction deployment, then remove the call to registerServiceWorker()\nfrom src/index.js.\nIf you had previously enabled service workers in your production deployment and\nhave decided that you would like to disable them for all your existing users,\nyou can swap out the call to registerServiceWorker() in\nsrc/index.js first by modifying the service worker import:\nand then call unregister() instead.\nAfter the user visits a page that has unregister(),\nthe service worker will be uninstalled. Note that depending on how /service-worker.js is served,\nit may take up to 24 hours for the cache to be invalidated.\nOffline-First Considerations\nService workers require HTTPS,\nalthough to facilitate local testing, that policy\ndoes not apply to localhost.\nIf your production web server does not support HTTPS, then the service worker\nregistration will fail, but the rest of your web app will remain functional.\nService workers are not currently supported\nin all web browsers. Service worker registration won't be attempted\non browsers that lack support.\nThe service worker is only enabled in the production environment,\ne.g. the output of npm run build. It's recommended that you do not enable an\noffline-first service worker in a development environment, as it can lead to\nfrustration when previously cached assets are used and do not include the latest\nchanges you've made locally.\nIf you need to test your offline-first service worker locally, build\nthe application (using npm run build) and run a simple http server from your\nbuild directory. After running the build script, create-react-app will give\ninstructions for one way to test your production build locally and the deployment instructions have\ninstructions for using other methods. Be sure to always use an\nincognito window to avoid complications with your browser cache.\nIf possible, configure your production environment to serve the generated\nservice-worker.js with HTTP caching disabled.\nIf that's not possible—GitHub Pages, for instance, does not\nallow you to change the default 10 minute HTTP cache lifetime—then be aware\nthat if you visit your production site, and then revisit again before\nservice-worker.js has expired from your HTTP cache, you'll continue to get\nthe previously cached assets from the service worker. If you have an immediate\nneed to view your updated production deployment, performing a shift-refresh\nwill temporarily disable the service worker and retrieve all assets from the\nnetwork.\nUsers aren't always familiar with offline-first web apps. It can be useful to\nlet the user know\nwhen the service worker has finished populating your caches (showing a \"This web\napp works offline!\" message) and also let them know when the service worker has\nfetched the latest updates that will be available the next time they load the\npage (showing a \"New content is available; please refresh.\" message). Showing\nthis messages is currently left as an exercise to the developer, but as a\nstarting point, you can make use of the logic included in src/registerServiceWorker.js, which\ndemonstrates which service worker lifecycle events to listen for to detect each\nscenario, and which as a default, just logs appropriate messages to the\nJavaScript console.\nBy default, the generated service worker file will not intercept or cache any\ncross-origin traffic, like HTTP API requests,\nimages, or embeds loaded from a different domain. If you would like to use a\nruntime caching strategy for those requests, you can eject\nand then configure the\nruntimeCaching\noption in the SWPrecacheWebpackPlugin section of\nwebpack.config.prod.js.\nProgressive Web App Metadata\nThe default configuration includes a web app manifest located at\npublic/manifest.json, that you can customize with\ndetails specific to your web application.\nWhen a user adds a web app to their homescreen using Chrome or Firefox on\nAndroid, the metadata in manifest.json determines what\nicons, names, and branding colors to use when the web app is displayed.\nThe Web App Manifest guide\nprovides more context about what each field means, and how your customizations\nwill affect your users' experience.\nAnalyzing the Bundle Size\nSource map explorer analyzes\nJavaScript bundles using the source maps. This helps you understand where code\nbloat is coming from.\nTo add Source map explorer to a Create React App project, follow these steps:\nAlternatively you may use yarn:\nThen in package.json, add the following line to scripts:\nThen to analyze the bundle run the production build then run the analyze\nscript.\nDeployment\nnpm run build creates a build directory with a production build of your app. Set up your favorite HTTP server so that a visitor to your site is served index.html, and requests to static paths like /static/js/main.<hash>.js are served with the contents of the /static/js/main.<hash>.js file.\nStatic Server\nFor environments using Node, the easiest way to handle this would be to install serve and let it handle the rest:\nThe last command shown above will serve your static site on the port 5000. Like many of serve’s internal settings, the port can be adjusted using the -p or --port flags.\nRun this command to get a full list of the options available:\nOther Solutions\nYou 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.\nHere’s a programmatic example using Node and Express:\nThe 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.\nThe build folder with static assets is the only output produced by Create React App.\nHowever 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.\nServing Apps with Client-Side Routing\nIf you use routers that use the HTML5 pushState history API under the hood (for example, 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.\nThis 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:\nIf you’re using Apache HTTP Server, you need to create a .htaccess file in the public folder that looks like this:\nIt will get copied to the build folder when you run npm run build.\nIf you’re using Apache Tomcat, you need to follow this Stack Overflow answer.\nNow requests to /todos/42 will be handled correctly both in development and in production.\nOn a production build, and in a browser that supports service workers,\nthe service worker will automatically handle all navigation requests, like for\n/todos/42, by serving the cached copy of your index.html. This\nservice worker navigation routing can be configured or disabled by\nejecting and then modifying the\nnavigateFallback\nand navigateFallbackWhitelist\noptions of the SWPreachePlugin configuration.\nWhen 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 and change start_url to match the required URL scheme, for example:\nBuilding for Relative Paths\nBy default, Create React App produces a build assuming your app is hosted at the server root.\nTo override this, specify the homepage in your package.json, for example:\nThis will let Create React App correctly infer the root path to use in the generated HTML file.\nNote: If you are using react-router@^4, you can root <Link>s using the basename prop on any <Router>.\nMore information here.\n\nFor example:\nNote: this feature is available with react-scripts@0.9.0 and higher.\nIf 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:\nThis 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.\nAzure\nSee this blog post on how to deploy your React app to Microsoft Azure.\nSee this blog post or this repo for a way to use automatic deployment to Azure App Service.\nFirebase\nInstall the Firebase CLI if you haven’t already by running npm install -g firebase-tools. Sign up for a Firebase account and create a new project. Run firebase login and login with your previous created Firebase account.\nThen 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.\nIMPORTANT: you need to set proper HTTP caching headers for service-worker.js file in firebase.json file or you will not be able to see changes after first deployment (issue #2440). It should be added inside \"hosting\" key like next:\nNow, after you create a production build with npm run build, you can deploy it by running firebase deploy.\nFor more information see Add Firebase to your JavaScript Project.\nGitHub Pages\nNote: this feature is available with react-scripts@0.2.0 and higher.\nThe step below is important!\nIf you skip it, your app will not deploy correctly.\nOpen your package.json and add a homepage field for your project:\nor for a GitHub user page:\nCreate React App uses the homepage field to determine the root URL in the built HTML file.\nNow, whenever you run npm run build, you will see a cheat sheet with instructions on how to deploy to GitHub Pages.\nTo publish it at https://myusername.github.io/my-app, run:\nAlternatively you may use yarn:\nAdd the following scripts in your package.json:\nThe predeploy script will run automatically before deploy is run.\nIf you are deploying to a GitHub user page instead of a project page you'll need to make two\nadditional modifications:\nThen run:\nFinally, make sure GitHub Pages option in your GitHub project settings is set to use the gh-pages branch:\n\nYou can configure a custom domain with GitHub Pages by adding a CNAME file to the public/ folder.\nGitHub 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:\nIf, when deploying, you get /dev/tty: No such a device or address or a similar error, try the follwing:\nHeroku\nUse the Heroku Buildpack for Create React App.\nYou can find instructions in Deploying React with Zero Configuration.\nSometimes npm run build works locally but fails during deploy via Heroku. Following are the most common cases.\nIf you get something like this:\nIt 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.\nThis 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.\nIf you exclude or ignore necessary files from the package you will see a error similar this one:\nIn this case, ensure that the file is there with the proper lettercase and that’s not ignored on your local .gitignore or ~/.gitignore_global.\nNetlify\nTo do a manual deploy to Netlify’s CDN:\nChoose build as the path to deploy.\nTo setup continuous delivery:\nWith this setup Netlify will build and deploy when you push to git or open a pull request:\nSupport for client-side routing:\nTo support pushState, make sure to create a public/_redirects file with the following rewrite rules:\nWhen you build the project, Create React App will place the public folder contents into the build output.\nNow\nNow offers a zero-configuration single-command deployment. You can use now to deploy your app for free.\nInstall the now command-line tool either via the recommended desktop tool or via node with npm install -g now.\nBuild your app by running npm run build.\nMove into the build directory by running cd build.\nRun now --name your-project-name from within the build directory. You will see a now.sh URL in your output like this:\nPaste that URL into your browser when the build is complete, and you will see your deployed app.\nDetails are available in this article.\nS3 and CloudFront\nSee this blog post on how to deploy your React app to Amazon Web Services S3 and CloudFront.\nSurge\nInstall 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.\nWhen asked about the project path, make sure to specify the build folder, for example:\nNote 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.\nAdvanced Configuration\nYou can adjust various development and production settings by setting environment variables in your shell or with .env.\nTroubleshooting\nnpm start doesn’t detect changes\nWhen you save a file while npm start is running, the browser should refresh with the updated code.\nIf this doesn’t happen, try one of the following workarounds:\nIf none of these solutions help please leave a comment in this thread.\nnpm test hangs on macOS Sierra\nIf 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 installation as described in facebookincubator/create-react-app#713.\nWe 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:\nIt is reported that installing Watchman 4.7.0 or newer fixes the issue. If you use Homebrew, you can run these commands to update it:\nYou can find other installation methods on the Watchman documentation page.\nIf this still doesn’t help, try running launchctl unload -F ~/Library/LaunchAgents/com.github.facebook.watchman.plist.\nThere are also reports that uninstalling Watchman fixes the issue. So if nothing else helps, remove it from your system and try again.\nnpm run build exits too early\nIt 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:\nThe 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.\nIf you are completely sure that you didn't terminate the process, consider adding some swap space to the machine you’re building on, or build the project locally.\nnpm run build fails on Heroku\nThis may be a problem with case sensitive filenames.\nPlease refer to this section.\nMoment.js locales are missing\nIf you use a Moment.js, 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.\nTo add a specific Moment.js locale to your bundle, you need to import it explicitly.\nFor example:\nIf import multiple locales this way, you can later switch between them by calling moment.locale() with the locale name:\nThis will only work for locales that have been explicitly imported before.\nnpm run build fails to minify\nSome 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.\nFork the package and publish a corrected version yourself.\nIf the dependency is small enough, copy it to your src/ folder and treat it as application code.\nIn 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.\nAlternatives to Ejecting\nEjecting lets you customize anything, but from that point on you have to maintain the configuration and scripts yourself. This can be daunting if you have many similar projects. In such cases instead of ejecting we recommend to fork react-scripts and any other packages you need. This article dives into how to do it in depth. You can find more discussion in this issue.\nSomething Missing?\nIf you have ideas for more “How To” recipes that should be on this page, let us know or contribute some!\nAbout\n\n An attempt to make a channel manager for Vacation Rentals\n \nResources\nStars\nWatchers\nForks\n\n\n Releases\n\n\n\n Packages\n 0\n\nLanguages\nFooter\nFooter navigation\n"}],"response_time":3.23}</article></body></html>