The `netlify-cms-proxy-server` is an Express-based proxy server designed to facilitate local development for Netlify CMS, which has since been rebranded as Decap CMS. It allows content editors to interact with a local Git repository via the CMS interface running on `localhost`, eliminating the need for a live Git backend during local development. The package's current version is 1.3.24, and it was last published approximately four years ago. Following the rebranding of Netlify CMS to Decap CMS in February 2023, this package has been superseded by `decap-server`, which provides equivalent functionality and is actively maintained. Users are strongly advised to migrate to `decap-server` for current features, support, and security updates, as `netlify-cms-proxy-server` is considered deprecated.
npm install netlify-cms-proxy-serverVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to start the proxy server using npx and configure your `config.yml` for local development. It also shows how to customize the port and repository directory via a `.env` file for the now-deprecated Netlify CMS Proxy Server. For current Decap CMS usage, substitute `netlify-cms-proxy-server` with `decap-server`.
Migrate to `decap-server` for local proxy functionality with Decap CMS. Uninstall `netlify-cms-proxy-server` and install `decap-server`.
Never expose `netlify-cms-proxy-server` or `decap-server` to public networks or use it in production. Ensure it only listens on `localhost` or `127.0.0.1`.
Always use a recent LTS version of Node.js (e.g., Node.js 18 or 20) to ensure compatibility across all Decap CMS components.
Explicitly set `branch: main` (or your repository's default branch) in your `config.yml` under the `backend` section when using a non-standard default branch name.
Verify that your `config.yml` settings (especially `proxy_url` and `branch`) are correct. Ensure the `npx netlify-cms-proxy-server` command is run from the root of a valid local Git repository and that the repository is correctly initialized.
Stop the conflicting application or configure a different port for the proxy server by creating a `.env` file in your repository root with `PORT=YOUR_CUSTOM_PORT` (e.g., `PORT=8082`). Update your `config.yml` `proxy_url` to match the new port.
Ensure the package is available. If using `npx`, it will try to download it. If running from `package.json` scripts, ensure `netlify-cms-proxy-server` is listed in your `devDependencies` and installed via `npm install` or `yarn install`.