@nextsparkjs/core 0.1.0-beta.186 → 0.1.0-beta.188

package/dist/templates/app/layout.ppr.tsx

@@ -79,7 +79,12 @@ export default async function RootLayout({
           <NextThemeProvider
             attribute="class"
             defaultTheme={DEFAULT_THEME_MODE}
-            enableSystem={DEFAULT_THEME_MODE === 'system'}
+            // Always true here: this layout never passes forcedTheme, so
+            // ThemeToggle is unconditionally visible and offers "System" as one
+            // of its 3 choices — gating on DEFAULT_THEME_MODE === 'system' had
+            // the same bug as the non-PPR layout (see #175): a build-time
+            // default of 'light'/'dark' silently broke the "System" option.
+            enableSystem
             disableTransitionOnChange
           >
             <CustomThemeProvider>

package/dist/templates/app/layout.tsx

@@ -81,8 +81,17 @@ export default async function RootLayout({
             defaultTheme={defaultMode}
             // When allowUserToggle is false, force the theme and ignore localStorage/system
             forcedTheme={!allowUserToggle ? defaultMode : undefined}
-            // Only detect OS preference when theme configures defaultMode: 'system' AND user can toggle
-            enableSystem={allowUserToggle && defaultMode === 'system'}
+            // Detect OS preference whenever the user can toggle at all. ThemeToggle
+            // always offers "System" as one of its 3 choices when toggling is
+            // allowed, so the provider must be able to resolve it whenever that's
+            // true — gating on `defaultMode === 'system'` looks equivalent at
+            // first render, but defaultMode is the user's last SAVED preference
+            // for a logged-in user (see getThemeSettings), not a static "is
+            // system-matching enabled" flag. That made "System" silently write a
+            // literal, unmatched `class="system"` for anyone whose saved
+            // preference (or the theme's own config default) wasn't already
+            // 'system' — see #175.
+            enableSystem={allowUserToggle}
             // Force a theme on the routes declared in theme.config.ts (forcedThemeRoutes)
             forcedThemeRoutes={forcedThemeRoutes}
             disableTransitionOnChange

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nextsparkjs/core",
-  "version": "0.1.0-beta.186",
+  "version": "0.1.0-beta.188",
   "description": "NextSpark - The complete SaaS framework for Next.js",
   "license": "MIT",
   "author": "NextSpark <hello@nextspark.dev>",
@@ -479,7 +479,7 @@
     "tailwind-merge": "^3.3.1",
     "uuid": "^13.0.0",
     "zod": "^4.3.6",
-    "@nextsparkjs/testing": "0.1.0-beta.186"
+    "@nextsparkjs/testing": "0.1.0-beta.188"
   },
   "scripts": {
     "postinstall": "node scripts/postinstall.mjs || true",

package/templates/app/layout.ppr.tsx

@@ -79,7 +79,12 @@ export default async function RootLayout({
           <NextThemeProvider
             attribute="class"
             defaultTheme={DEFAULT_THEME_MODE}
-            enableSystem={DEFAULT_THEME_MODE === 'system'}
+            // Always true here: this layout never passes forcedTheme, so
+            // ThemeToggle is unconditionally visible and offers "System" as one
+            // of its 3 choices — gating on DEFAULT_THEME_MODE === 'system' had
+            // the same bug as the non-PPR layout (see #175): a build-time
+            // default of 'light'/'dark' silently broke the "System" option.
+            enableSystem
             disableTransitionOnChange
           >
             <CustomThemeProvider>

package/templates/app/layout.tsx

@@ -81,8 +81,17 @@ export default async function RootLayout({
             defaultTheme={defaultMode}
             // When allowUserToggle is false, force the theme and ignore localStorage/system
             forcedTheme={!allowUserToggle ? defaultMode : undefined}
-            // Only detect OS preference when theme configures defaultMode: 'system' AND user can toggle
-            enableSystem={allowUserToggle && defaultMode === 'system'}
+            // Detect OS preference whenever the user can toggle at all. ThemeToggle
+            // always offers "System" as one of its 3 choices when toggling is
+            // allowed, so the provider must be able to resolve it whenever that's
+            // true — gating on `defaultMode === 'system'` looks equivalent at
+            // first render, but defaultMode is the user's last SAVED preference
+            // for a logged-in user (see getThemeSettings), not a static "is
+            // system-matching enabled" flag. That made "System" silently write a
+            // literal, unmatched `class="system"` for anyone whose saved
+            // preference (or the theme's own config default) wasn't already
+            // 'system' — see #175.
+            enableSystem={allowUserToggle}
             // Force a theme on the routes declared in theme.config.ts (forcedThemeRoutes)
             forcedThemeRoutes={forcedThemeRoutes}
             disableTransitionOnChange

package/dist/lib/config/index.d.js

@@ -1,7 +0,0 @@
-export * from "./config-utils.js";
-export * from "./config-loader.js";
-export * from "./config-sync.js";
-import { defineConfig } from "./nextspark-types.js";
-export {
-  defineConfig
-};

package/dist/lib/email/index.d.js

@@ -1,3 +0,0 @@
-export * from "./types.js";
-export * from "./factory.js";
-export * from "./templates.js";

package/dist/lib/scheduled-actions/index.d.js

@@ -1,19 +0,0 @@
-import { registerScheduledAction, getActionHandler, getAllRegisteredActions, isActionRegistered, clearActionRegistry } from "./registry.js";
-import { scheduleAction, scheduleRecurringAction, cancelScheduledAction } from "./scheduler.js";
-import { processPendingActions } from "./processor.js";
-import { cleanupOldActions } from "./cleanup.js";
-import { initializeScheduledActions, initializeRecurringActions } from "./initializer.js";
-export {
-  cancelScheduledAction,
-  cleanupOldActions,
-  clearActionRegistry,
-  getActionHandler,
-  getAllRegisteredActions,
-  initializeRecurringActions,
-  initializeScheduledActions,
-  isActionRegistered,
-  processPendingActions,
-  registerScheduledAction,
-  scheduleAction,
-  scheduleRecurringAction
-};

package/dist/lib/scheduled-actions/initializer.d.js

@@ -1 +0,0 @@
-import "server-only";

package/dist/lib/services/index.d.js

@@ -1,40 +0,0 @@
-import { UserService } from "./user.service.js";
-import { MetaService } from "./meta.service.js";
-import { PlanService } from "./plan.service.js";
-import { SubscriptionService } from "./subscription.service.js";
-import { UsageService } from "./usage.service.js";
-import { InvoiceService } from "./invoice.service.js";
-import { TeamService } from "./team.service.js";
-import { TeamMemberService } from "./team-member.service.js";
-import { PermissionService } from "./permission.service.js";
-import { MembershipService, TeamMembership } from "./membership.service.js";
-import { ThemeService } from "./theme.service.js";
-import { EntityTypeService } from "./entity-type.service.js";
-import { NamespaceService } from "./namespace.service.js";
-import { MiddlewareService } from "./middleware.service.js";
-import { ScopeService } from "./scope.service.js";
-import { RouteHandlerService } from "./route-handler.service.js";
-import { PluginService, usePlugin } from "./plugin.service.js";
-import { ApiRoutesService } from "./api-routes.service.js";
-export {
-  ApiRoutesService,
-  EntityTypeService,
-  InvoiceService,
-  MembershipService,
-  MetaService,
-  MiddlewareService,
-  NamespaceService,
-  PermissionService,
-  PlanService,
-  PluginService,
-  RouteHandlerService,
-  ScopeService,
-  SubscriptionService,
-  TeamMemberService,
-  TeamMembership,
-  TeamService,
-  ThemeService,
-  UsageService,
-  UserService,
-  usePlugin
-};