create-elytra 0.0.0 → 0.0.1

package/template/studio/vite.config.ts

@@ -0,0 +1,26 @@
+import { defineConfig } from 'vite'
+import { tanstackStart } from '@tanstack/react-start/plugin/vite'
+import viteReact from '@vitejs/plugin-react'
+import tailwindcss from '@tailwindcss/vite'
+
+/**
+ * EC-223 mount contract: no `@site/*` alias and no per-package `src` alias. A real
+ * consumer pulls the engine from its published/linked package, not from elytra repo
+ * source paths. In dev, Vite's default `development` export condition resolves the
+ * linked `@elytracms/*` packages to their TypeScript source (the iterate-fast loop,
+ * EC-231); a production build (EC-234, registry install) resolves `default` → `dist`.
+ * `ssr.noExternal` transpiles the linked packages through Vite's SSR pipeline.
+ */
+export default defineConfig({
+  // EC-234 — the studio is a pure client app: Convex serves all data + auth, and
+  // there are no server functions/loaders (no createServerFn, no API routes). Build
+  // it as a static SPA (a prerendered `dist/client/index.html` shell + client bundle)
+  // so any static host — Vercel here — can serve it with a catch-all → index.html
+  // rewrite. The default SSR build emits dist/{client,server} with no servable root
+  // index.html, which on Vercel's static target 404s every route.
+  plugins: [tailwindcss(), tanstackStart({ spa: { enabled: true } }), viteReact()],
+  server: { port: 5180 },
+  ssr: {
+    noExternal: [/^@elytracms\//],
+  },
+})

package/template/turbo.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://turbo.build/schema.json",
+  "tasks": {
+    "build": {
+      "outputs": [".next/**", "dist/**"]
+    },
+    "dev": {
+      "cache": false,
+      "persistent": true
+    },
+    "lint": {
+      "outputs": []
+    },
+    "type-check": {
+      "outputs": []
+    }
+  }
+}