---
title: "Disconnected mode support in JSS for Angular"
slug: "disconnected-mode-support-in-jss-for-angular"
abstract: "Description of how JSS Angular apps support disconnected mode."
---
# Disconnected mode support in JSS for Angular

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").

The JSS application for Angular runs a small Express server on a different port that hosts the mock services. The default port is 3043. This Express server hosts the mock services. You can inspect this proxy for running the application in disconnected mode in `scripts/disconnected-mode-proxy.ts`.

The `/proxy.conf.js` file contains configuration for the `angular-cli` to proxy requests to API paths to the mock service layer.

The mock service 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 `/data` and `/sitecore/definitions`) directories. This manifest regenerates automatically when you change the data. The application supports live reloading for such data changes.