---
title: "Disconnected mode support in the JSS React app"
slug: "disconnected-mode-support-in-the-jss-react-app"
abstract: "Description of how JSS React apps support disconnected mode."
---
# Disconnected mode support in the JSS React app

The JSS [disconnected mode](https://doc.sitecore.com/xp/en/developers/hd/21/sitecore-headless-development/start-a-jss-app-in-disconnected-mode.html "Start a JSS app in disconnected mode") enables the development of JSS apps using a local mock version of the [Sitecore Headless Services](https://doc.sitecore.com/xp/en/developers/hd/21/sitecore-headless-development/sitecore-headless-services.html "Sitecore Headless Services") - [Layout Service](https://doc.sitecore.com/xp/en/developers/hd/21/sitecore-headless-development/layout-service.html "Layout Service") and [Dictionary Service](https://doc.sitecore.com/xp/en/developers/hd/21/sitecore-headless-development/dictionary-service.html "Dictionary Service").

When starting the JSS application for React in disconnected mode, the app runs a small Express application on a different port that hosts the mock services. The default port is 3042. The application proxies all requests to API paths to this mock service layer. You can inspect and customize this proxy for running the application in disconnected mode in the `scripts/disconnected-mode-proxy.js` file.

The application is built with[`create-react-app`](https://create-react-app.dev/), which allows [manual configuration of proxy behavior](https://create-react-app.dev/docs/proxying-api-requests-in-development/#configuring-the-proxy-manually). Refer to the `src/setupProxy.js` file, where you can inspect different proxy configurations. When running the application in disconnected mode, the setup in this file enables the proxying of API requests to the mock server.

The mock services layer is powered by an automatically generated [JSS manifest](https://doc.sitecore.com/xp/en/developers/hd/21/sitecore-headless-development/jss-manifest-api.html "JSS Manifest API") file. The file is generated from disconnected data definitions in the directories `/data` and `/sitecore/definitions`. This manifest regenerates automatically when you change the data. The application supports live reloading for such data changes.