@salesforce/storefront-next-dev 1.0.0-alpha.1 → 1.0.0-alpha.3

package/dist/commands/create-storefront.js

@@ -100,6 +100,12 @@ const createStorefront = async (options = {}) => {
 		recursive: true,
 		force: true
 	});
+	let templateRelease;
+	const generatedPkgPath = path.join(outputPath, "package.json");
+	if (fs.existsSync(generatedPkgPath)) try {
+		templateRelease = JSON.parse(fs.readFileSync(generatedPkgPath, "utf8"))?.storefrontNext?.templateRelease;
+	} catch {}
+	if (!templateRelease) logger.warn("This template is missing its \"storefrontNext\" origin metadata in package.json. You can still build and run it, but it won’t record which template release it came from.");
 	const workspaceYamlPath = path.join(outputPath, "pnpm-workspace.yaml");
 	if (!fs.existsSync(workspaceYamlPath)) logger.warn(`Template is missing pnpm-workspace.yaml at ${workspaceYamlPath}. The generated project may not work correctly without a workspace configuration.`);
 	if (isLocalPath(template) || options.localPackagesDir) {
@@ -173,7 +179,7 @@ const createStorefront = async (options = {}) => {
     ║                       CONGRATULATIONS                            ║
     ╚══════════════════════════════════════════════════════════════════╝
 
-        🎉 Congratulations! Your storefront is ready to use! 🎉
+        🎉 Congratulations! Your storefront is ready to use! 🎉${templateRelease ? `\n        📦 Generated from template release: ${templateRelease}` : ""}
         What's next:
         - Navigate to the storefront directory: cd ${outputPath}
         - Install dependencies: pnpm install

package/dist/index.js

@@ -1796,6 +1796,17 @@ function i18nPlugin(config) {
 * - `optimizeDeps.include`: forces Vite's dep optimizer to pre-bundle
 *   `react-router` and its `/internal/react-server-client` entry so the
 *   React Router dev plugin resolves a single shared instance on the client.
+*   It also pre-bundles the React-importing entry points of the runtime SDK
+*   (`/config`, `/security/react`, `/site-context`, `/design/react/core`,
+*   `/routing/app-wrapper`, `/i18n/client`). Without this, Vite optimizes the
+*   app's own React first, then *discovers* these SDK subpaths the first time a
+*   component imports them at request time, triggers a dep re-optimization, and
+*   forces a full-page reload. During that window the SDK's React hooks
+*   (`useConfig` → `useContext`) momentarily resolve against a second, freshly
+*   optimized React instance — surfacing as "Invalid hook call" / "Cannot read
+*   properties of null (reading 'useContext')" until the reload settles.
+*   Including them up front means a single first-pass optimization with one
+*   shared React, so no mid-session re-optimize and no transient duplicate.
 * - `ssr.noExternal`: forces the SDK through Vite's SSR transform pipeline
 *   in dev. The SDK exports module-level singletons (router contexts, etc.)
 *   whose object identity is load-bearing — they're used as `Map` keys, so
@@ -1824,7 +1835,18 @@ const baseConfigPlugin = () => ({
 				"react-dom",
 				"react-router"
 			] },
-			optimizeDeps: { include: ["react-router", "react-router/internal/react-server-client"] },
+			optimizeDeps: { include: [
+				"react-router",
+				"react-router/internal/react-server-client",
+				"@salesforce/storefront-next-runtime/config",
+				"@salesforce/storefront-next-runtime/security/react",
+				"@salesforce/storefront-next-runtime/site-context",
+				"@salesforce/storefront-next-runtime/design/react/core",
+				"@salesforce/storefront-next-runtime/routing/app-wrapper",
+				"@salesforce/storefront-next-runtime/i18n/client",
+				"i18next-browser-languagedetector",
+				"remix-i18next/middleware"
+			] },
 			ssr: { noExternal: ["@salesforce/storefront-next-runtime"] }
 		};
 	}