create-vexcms 0.1.0-alpha.10 → 0.1.0-alpha.12

package/README.md

@@ -1,5 +1,15 @@
 # create-vexcms
 
+> [!WARNING]
+> `create-vexcms` is pre-release software, published only under the `alpha` npm
+> dist-tag (`0.1.0-alpha.x`) — the `latest` tag on npm still points at an old,
+> unrelated `0.0.20` line, so always scaffold with an explicit tag:
+> `pnpm create vexcms@alpha`. Use it for experiments and evaluation only; the
+> projects it scaffolds should not carry production traffic or real user data.
+> Breaking changes land between alpha releases without deprecation cycles, and
+> there is no migration path between alphas. See the
+> [roadmap](https://docs.vexcms.dev) for what is and is not shipped.
+
 Scaffolding CLI for [VexCMS](https://github.com/ianyimi/vex) projects. Creates a complete
 Next.js application with a Convex backend, Better Auth authentication, and a self-hosted admin
 panel — ready to run.
@@ -7,19 +17,19 @@ panel — ready to run.
 ## Usage
 
 ```bash
-pnpm create vexcms@latest
+pnpm create vexcms@alpha
 ```
 
 Or with a project name:
 
 ```bash
-pnpm create vexcms@latest my-project
+pnpm create vexcms@alpha my-project
 ```
 
 Supports relative paths, including scaffolding straight into a monorepo app directory:
 
 ```bash
-pnpm create vexcms@latest apps/website
+pnpm create vexcms@alpha apps/website
 ```
 
 ## Flags
@@ -33,16 +43,16 @@ pnpm create vexcms@latest apps/website
 
 ```bash
 # Empty project, no pre-built collections
-pnpm create vexcms@latest my-app --bare
+pnpm create vexcms@alpha my-app --bare
 
 # Project with multi-tenant organizations
-pnpm create vexcms@latest my-app --orgs
+pnpm create vexcms@alpha my-app --orgs
 
 # Non-interactive, defaults only
-pnpm create vexcms@latest my-app --yes
+pnpm create vexcms@alpha my-app --yes
 
 # Inside a pnpm workspace, catalog-aware
-pnpm create vexcms@latest my-app --monorepo --yes
+pnpm create vexcms@alpha my-app --monorepo --yes
 ```
 
 ## Interactive prompts
@@ -157,7 +167,7 @@ Run from inside an existing pnpm workspace to scaffold a new app under it instea
 standalone project:
 
 ```bash
-pnpm create vexcms@latest my-app --monorepo --yes
+pnpm create vexcms@alpha my-app --monorepo --yes
 ```
 
 The installer walks up from the current directory for the nearest `pnpm-workspace.yaml`, targets
@@ -168,11 +178,12 @@ versions), and skips both `git init` and dependency install — the root workspa
 ## Versioning
 
 `create-vexcms` is versioned alongside every `@vexcms/*` package. Running
-`pnpm create vexcms@latest` always scaffolds with the latest package versions; pin a specific
-release the same way:
+`pnpm create vexcms@alpha` always scaffolds with the newest pre-release. The npm
+`latest` tag still points at an old, unrelated `0.0.20` line, so `@alpha` — or an
+exact version — is the only way to get the current API:
 
 ```bash
-pnpm create vexcms@0.1.0
+pnpm create vexcms@0.1.0-alpha.10
 ```
 
 The scaffolded project's `@vexcms/*` dependencies match the version of `create-vexcms` used to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-vexcms",
-  "version": "0.1.0-alpha.10",
+  "version": "0.1.0-alpha.12",
   "description": "Scaffold a new VexCMS project",
   "keywords": [
     "cms",

package/templates/base-nextjs/convex/auth/options.ts

@@ -1,5 +1,7 @@
 import type { BetterAuthOptions } from "better-auth"
 
+import { anonRoleDatabaseHook } from "@vexcms/better-auth"
+
 import {
   TABLE_SLUG_ACCOUNTS,
   TABLE_SLUG_SESSIONS,
@@ -15,6 +17,13 @@ export const authOptions: BetterAuthOptions = {
     modelName: TABLE_SLUG_ACCOUNTS,
   },
   baseURL: process.env.SITE_URL,
+  databaseHooks: {
+    // Ties Better Auth's anonymous-plugin users to `access.anonRole` (see
+    // `~/auth/access.ts`) by stamping the same role explicitly, rather than
+    // relying solely on `roles`' `defaultValue` below — which every new user
+    // gets regardless of `isAnonymous`, anon-plugin or not.
+    user: anonRoleDatabaseHook(USER_ROLES.user),
+  },
   // {{EMAIL_PASSWORD_AUTH}}
   // {{OAUTH_PROVIDERS}}
   plugins: createPlugins(),

package/templates/base-nextjs/package.json

@@ -24,11 +24,11 @@
     "@t3-oss/env-nextjs": "0.13.11",
     "@tanstack/react-form": "1.33.1",
     "@tanstack/react-query": "5.101.2",
-    "@vexcms/better-auth": "~0.1.0-alpha.10",
-    "@vexcms/core": "~0.1.0-alpha.10",
-    "@vexcms/file-storage-convex": "~0.1.0-alpha.10",
-    "@vexcms/next": "~0.1.0-alpha.10",
-    "@vexcms/react": "~0.1.0-alpha.10",
+    "@vexcms/better-auth": "~0.1.0-alpha.12",
+    "@vexcms/core": "~0.1.0-alpha.12",
+    "@vexcms/file-storage-convex": "~0.1.0-alpha.12",
+    "@vexcms/next": "~0.1.0-alpha.12",
+    "@vexcms/react": "~0.1.0-alpha.12",
     "better-auth": "1.6.23",
     "class-variance-authority": "0.7.1",
     "clsx": "2.1.1",
@@ -52,7 +52,7 @@
     "@types/node": "20.19.43",
     "@types/react": "19.2.17",
     "@types/react-dom": "19.2.3",
-    "@vexcms/cli": "~0.1.0-alpha.10",
+    "@vexcms/cli": "~0.1.0-alpha.12",
     "babel-plugin-react-compiler": "1.0.0",
     "eslint": "9.39.5",
     "eslint-config-next": "15.5.9",

package/templates/base-nextjs/src/components/providers/server.tsx

@@ -3,16 +3,29 @@ import { NuqsAdapter } from "nuqs/adapters/next/app";
 import { type PropsWithChildren } from "react";
 
 import { AuthServerProvider } from "./auth";
-import ConvexClientProvider from "./convex";
 
+/**
+ * Server-side provider shell.
+ *
+ * Deliberately does **not** mount `ConvexClientProvider` — `ClientProviders`
+ * renders it, and `ClientProviders` is nested inside this component, so its
+ * copy is the one that actually reaches `children`. Mounting it here as well
+ * built a second `ConvexReactClient` + `QueryClient` pair on every server
+ * render (`providers/convex.tsx` intentionally creates fresh clients per call
+ * server-side to avoid cross-request leaks) whose only consumer was the
+ * discarded outer subtree.
+ *
+ * Nothing between here and `ClientProviders` needs Convex: `AuthServerProvider`
+ * is a server component that calls `getToken()`/`fetchAuthQuery` directly, and
+ * `NuqsAdapter` is unrelated. React context is unreadable from server
+ * components regardless.
+ */
 export default function ServerProviders({ children }: PropsWithChildren) {
   return (
     <ThemeProvider defaultTheme="system">
-      <ConvexClientProvider>
-        <AuthServerProvider>
-          <NuqsAdapter>{children}</NuqsAdapter>
-        </AuthServerProvider>
-      </ConvexClientProvider>
+      <AuthServerProvider>
+        <NuqsAdapter>{children}</NuqsAdapter>
+      </AuthServerProvider>
     </ThemeProvider>
   );
 }

package/templates/marketing-site/convex/seed.ts

@@ -572,15 +572,6 @@ export const init = internalMutation({
     title: text({ label: "Title", required: true }),
     slug: text({ label: "Slug", required: true, index: "by_slug" }),
     excerpt: text({ label: "Excerpt" }),
-    status: select({
-      label: "Status",
-      options: [
-        { label: "Draft", value: "draft" },
-        { label: "Published", value: "published" },
-      ],
-      defaultValue: ["draft"],
-    }),
-    publishedAt: date({ label: "Published At" }),
     featured: checkbox({ label: "Featured" }),
     readingMinutes: number({ label: "Reading Minutes" }),
     coverImage: upload({ to: "images", label: "Cover Image" }),
@@ -612,8 +603,6 @@ export const posts = defineTable({
   title: v.string(),
   slug: v.string(),
   excerpt: v.optional(v.string()),
-  status: v.optional(v.array(v.union(v.literal("draft"), v.literal("published")))),
-  publishedAt: v.optional(v.number()),
   featured: v.optional(v.boolean()),
   readingMinutes: v.optional(v.number()),
   coverImage: v.optional(v.array(v.id("images"))),

package/templates/marketing-site/src/vexcms/blocks/FAQ/config.ts

@@ -35,7 +35,7 @@ export const faqBlock = defineBlock({
         {
           question: "What is Vex CMS?",
           answer:
-            "Vex CMS is a headless content management system built on Convex. It provides real-time data, type-safe schemas, draft/publish workflows, live preview, and a beautiful admin panel — all configured with TypeScript.",
+            "Vex CMS is a headless content management system built on Convex. It provides real-time data, type-safe schemas, database-driven theming, role-based access control, and a full admin panel — all configured in TypeScript. Versioning, drafts, and live preview are in progress; see the roadmap.",
         },
         {
           question: "How is Vex different from other headless CMS platforms?",