Next.js Starter Storefront
create-medusa-app. The standalone Next.js Starter Storefront is now deprecated.The Medusa application is made up of a Node.js server and an admin dashboard. The storefront is hosted separately from the Medusa application. You have the flexibility to choose the frontend tech stack that you and your team are proficient in, and implement unique design systems and user experience.
The Next.js Starter Storefront is a good place to start building your storefront. It provides rich commerce features and a sleek design. Developers and businesses can use it as-is or build on top of it to tailor it for the business's unique use case, design, and customer experience.
Installation#
Approach 1: Install with Medusa Application#
If you don't have a Medusa application installed, run the following command to install both the Medusa application and the Next.js Starter storefront:
You'll be asked for the project's name, then the installation will start.
The command will create a {project-name} directory that holds a monorepository. The Medusa backend will be installed in the apps/backend directory, and the Next.js Starter storefront will be installed in the apps/storefront directory.
Once the installation is done, the Medusa Admin dashboard will open in your default browser at http://localhost:9000/app, and the Next.js Starter storefront will be running at http://localhost:8000.
For other information related to the Medusa application's installation, refer to the Installation guide.
Approach 2: Install separately#
If you already have a Medusa monorepo installed and want to add the Next.js Starter storefront to it, follow these steps.
- From the root of your monorepo, clone the DTC Starter into a temporary directory to extract the storefront:
- Copy the storefront into your project's
appsdirectory, then remove the temporary clone:
- Make sure your workspace configuration includes the
apps/storefrontdirectory. If yourpnpm-workspace.yamlor theworkspacesfield inpackage.jsonalready uses a glob likeapps/*, no change is needed. Otherwise, add it explicitly:
- From the monorepo root, install the dependencies:
- Create the storefront's environment file from its template:
- In
apps/storefront/.env.local, set the URL of your Medusa backend and your publishable API key. You can retrieve the publishable API key from the Medusa Admin dashboard by going to Settings > API Key Management:
- While the Medusa application is running, start the Next.js Starter storefront from the
apps/storefrontdirectory:
Your Next.js Starter storefront is now running at http://localhost:8000.
Troubleshooting#
Installing Next.js Starter with create-medusa-app not working
CORS Error
Resolve "Cannot find module X" Errors
Issues when installing with Node v25+
Payment Providers#
Stripe Integration#
The Next.js Starter storefront is compatible with Medusa's Stripe Module Provider.
In your Next.js Starter project, set the following environment variables for the Stripe integration:
Where <YOUR_PUBLISHABLE_KEY> is your Stripe publishable key. You can retrieve it from your Stripe dashboard by going to Developers → API Keys.
Then, restart the Next.js Starter storefront. You can now use Stripe during checkout.
Change Medusa Application URL#
By default, the Medusa application runs at http://localhost:9000. This value is defined in your Next.js Starter storefront under the environment variable MEDUSA_BACKEND_URL.
To change the URL of the Medusa application in the storefront, set the MEDUSA_BACKEND_URL environment variable:
Change Medusa Publishable API Key#
All requests made from a storefront must pass a publishable API key in the request's header. This API key is created in the Medusa application. If you've installed the Next.js Starter storefront using create-medusa-app, the publishable API key is set in the environment variables automatically.
If you change your Medusa application or its database, or you lose the publishable API key you had before, make sure to change the NEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY environment variable to the new publishable API key: