---
schema_version: "1"
id: 91996214a9df3d05b74028a3b88869025ba550c38a6ffd26ffc8317a4b68704d
title: Troubleshooting Tips for Storefront Next
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/sfnext/guides/sfnext-debug-troubleshoot.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/sfnext-debug-troubleshoot.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: b8295c1252e4f3d92b43bb51ac427c4d4e423ec32fcac60b6d965164f787bcc7
products:
  - Composable Storefront
  - Salesforce APIs
---
# Troubleshooting Tips for Storefront Next

Before following the targeted advice in this guide, try these general troubleshooting steps.

- Double-check that you’re running a supported version of Node before starting your local development server.
- Confirm that your development server is still running and the port hasn’t been taken over by another process.
- After saving a code change, the browser updates automatically via Hot Module Replacement (HMR). If the change doesn't appear, check the terminal for build errors before forcing a reload.
- Look for errors in both the browser console and in the terminal.
- Look for network error responses using your browser’s developer tools. (In Chrome’s DevTools, go to the **Network** tab.)
- To help identify syntax errors and typos, run a code formatter and a linter. The command for running lint is `pnpm lint` for checking and `pnpm lint:fix` for auto-fixing lint issues. Configuration files are provided for both [Prettier](https://prettier.io/) (code formatter) and [ESLint](https://eslint.org/) (linter) in the Storefront Next app.
- To catch TypeScript errors that don't show up at run time, run `pnpm typecheck`.
- To see SCAPI requests and internal state changes, run `SFCC_LOG_LEVEL=debug pnpm dev` to increase log verbosity.
- Check your computer’s antivirus and firewall settings for anything that is preventing your code from running or blocking network requests.
- To identify and analyze performance issues, use the Profiler in Chrome’s DevTools. For more information, see this guide from Google: [Analyze Runtime Performance](https://developer.chrome.com/docs/devtools/performance). You can also install the React Developer Tools extension for Chrome to get another Profiler tab where you can see similar info but at the component level.