Medusa Starter Default
https://github.com/medusajs/medusa-starter-default- Category
- Developer Tools
- Rank
- No. 998Tools index
Previous survey · No. 983 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- medusajs
- GitHub
- 207 stars
- Date
About
Official default starter template for spinning up a Medusa commerce backend in seconds — the recommended way to start a new project.
What it does
This TypeScript project supplies a working Medusa 2 backend foundation. Configuration reads database, cross-origin, authentication, and secret settings from the environment. Extension points expose custom admin and store routes, while a seed workflow creates realistic commerce data for local development.
Why it's ranked here
The starter remains a useful reference for Medusa backend structure, especially its substantial seed workflow and clear extension points. However, the repository explicitly marks itself deprecated and directs new users to another starter. That warning outweighs its convenience for greenfield adoption.
What's good
The seed data exercises real commerce relationships instead of creating a toy product alone. It configures currencies, a European region, tax regions, warehouse inventory, sales channels, shipping profiles, fulfillment zones, shipping options, a publishable API key, categories, products, variants, and prices. Separate admin and store route examples show where backend customization begins.
Tradeoffs
The project is deprecated, so it should not anchor a new production codebase. Environment setup remains necessary, including a database URL and cross-origin settings. Authentication secrets fall back to a plainly insecure development value when omitted. The included HTTP coverage checks only server health, while other configured test categories have no supplied examples in the provided tree.
How to use it well
Use it to study Medusa 2 project anatomy, prototype backend extensions, or understand how commerce seed workflows connect modules. Run it with Node 20 or newer and supply proper environment secrets. For a new store, follow the repository’s replacement recommendation. This project does not provide a customer-facing storefront.
Technical notes+
package.json defines Yarn-based Node packaging, requires Node >=20, and exposes build, seed, start, development, HTTP integration, module integration, and unit-test scripts through the Medusa CLI. medusa-config.ts loads DATABASE_URL, STORE_CORS, ADMIN_CORS, AUTH_CORS, JWT_SECRET, and COOKIE_SECRET. src/scripts/seed.ts composes workflows from @medusajs/medusa/core-flows and resolves framework modules through the dependency container. src/api/admin/custom/route.ts and src/api/store/custom/route.ts each export a GET handler returning HTTP 200. jest.config.js selects test patterns through TEST_TYPE and transforms TypeScript with @swc/jest. integration-tests/http/health.spec.ts runs Medusa in-process and verifies the health endpoint. instrumentation.ts contains a commented OpenTelemetry example.
Observed
- License
- MIT
- Primary language
- TypeScript
- Runtime
- Node.js 20 or newer
- Package manager
- Yarn 4 with the node-modules linker
- Install surface
- Node package with Medusa framework, CLI, admin SDK, and backend dependencies
- Interfaces
- Medusa CLI scripts and HTTP routes for admin and store APIs
- Compatibility
- Medusa version 2 or newer
- Repository status
- Deprecated; README directs users to the dtc-starter replacement
Read from README.md, package.json, src/scripts/seed.ts, src/admin/vite-env.d.ts, src/admin/i18n/index.ts, src/api/admin/custom/route.ts, src/api/store/custom/route.ts, jest.config.js, medusa-config.ts, instrumentation.ts, integration-tests/setup.js, integration-tests/http/health.spec.ts, .yarnrc.yml, .env.template.
What it can do
Generate Medusa commerce backend project structure
Project initialization command → Complete Medusa backend codebase with default configuration
Set up database schema for e-commerce
Database connection parameters → Initialized database with commerce tables and relationships
Configure product management APIs
Template configuration → REST endpoints for product CRUD operations
Initialize order processing system
Default template settings → Order management workflows and API endpoints
Set up customer authentication
Template configuration → Customer login/registration system with JWT tokens
Configure payment processing framework
Default payment provider settings → Payment handling infrastructure and webhooks
Generate admin dashboard backend
Template initialization → Admin API endpoints for commerce management
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.