sfnext-configuration
Configure a Storefront Next app: config.server.ts (defineConfig, metadata/runtime/app), AppConfig types in src/types/config.ts, PUBLIC__ environment variable overrides, getConfig(context) / useConfig(), extension config (app.extension, app.serverExtension), protected paths, server-only secrets, and multi-site settings (commerce.sites, url.prefix, seoRoutes, siteAliasMap, cookie domain). Use when editing config.server.ts, adding a config value, an env var is ignored or "not applied", pnpm config:inspect / config:push-env, "Ignoring environment variable" warnings, protected config path errors, setting up a second site or locale URLs, or going through the pre-launch config checklist. Do not use for creating a project or the npm script list (use storefront-next:sfnext-project-setup), pushing bundles or MRT env management (use storefront-next:sfnext-deployment / b2c-cli:b2c-mrt), or hybrid proxy and cookie-sharing with SFRA (use storefront-next:sfnext-hybrid-storefronts).
Pinned to revision fe78868e0e70, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/sfnext-configuration/SKILL.md
- skills/sfnext-configuration/evals/trigger-evals.json
- skills/sfnext-configuration/references/ENV-VARIABLES.md
- skills/sfnext-configuration/references/MULTI-SITE-URLS.md
Every link opens the file at its source, pinned to the revision this page describes.