How reactioncommerce/reaction works
Project type and purpose
• This is a monorepo for Mailchimp Open Commerce (formerly Reaction Commerce): an API-first, headless commerce platform.
• Built with Node.js, MongoDB and GraphQL.
• Uses a plugin architecture: a core API plus dozens of domain-specific plugins (accounts, carts, orders, payments, etc).
• Provides both API (apps/reaction) and example frontends (apps/meteor-blaze-app).
File structure
• Top level: configuration (Docker, CircleCI, ESLint, pnpm-workspace), root package.json.
• apps/meteor-blaze-app: sample Meteor Blaze storefront.
• apps/reaction: the GraphQL API server, uses .env, Dockerfile, src/index.js, schema and plugin loader.
• packages/api-core: the heart of the GraphQL/Apollo server and plugin loader.
• packages/api-plugin-*: each subfolder is a self-contained GraphQL plugin (accounts, carts, catalogs, discounts, etc).
• packages/*: utility libraries (api-utils, file-collections, logger, random, etc).
• docker-compose*.yml: dev & CI orchestration.
• pnpm-workspace.yaml: monorepo package management.
README for additional insights
• Confirms Node.js + GraphQL + MongoDB stack.
• Plugin-based, multi-tenant, scalable.
• CLI driven (“reaction” CLI to scaffold and run API, admin, storefront).
• Uses changesets for versioning and CircleCI for automation.
Essential details
• Monorepo boundary and workspace manager (pnpm).
• Dynamic plugin loading at startup in the API server.
• CI/CD flow: GitHub → CircleCI → npm registry.