create-fluixi 0.1.0-alpha.8 → 0.1.0-alpha.9

package/README.md

@@ -24,13 +24,20 @@ pnpm create fluixi my-app
 yarn create fluixi my-app
 ```
 
-It prompts for a project name and a **mode**, or take them on the command line:
+It prompts for a project name, a **mode** and an **authoring format**, or takes them on the
+command line:
 
 ```bash
-create-fluixi my-app --ssr   # SSR app (@fluixi/start: file routing + SSR + hydration)
-create-fluixi my-app --spa   # SPA (vite + @fluixi/vite-plugin)
+create-fluixi my-app --ssr           # SSR app (@fluixi/start: file routing + SSR + hydration)
+create-fluixi my-app --spa           # SPA (vite + @fluixi/vite-plugin)
+
+create-fluixi my-app --spa --html    # same app, html`` templates instead of JSX
 ```
 
+`--jsx` (default) or `--html` picks how you write components. The html`` variant is
+JSX-free — plain `.ts` files, no `jsxImportSource`, and [`@fluixi/ts-plugin`](../ts-plugin)
+wired up so the editor still understands the templates. Both compile to the same thing.
+
 Then:
 
 ```bash
@@ -46,6 +53,9 @@ pnpm dev
 | **SSR** | [`@fluixi/start`](../start) + [`@fluixi/cli`](../cli) | `src/entry-{server,client}`, `src/routes/`, `fluixi.config.ts` |
 | **SPA** | `vite` + [`@fluixi/vite-plugin`](../vite-plugin) | `src/main.tsx` → `render(() => <App/>)` |
 
+Each comes in a JSX and an html`` variant (`template-ssr`, `template-ssr-html`, and the same
+two for SPA).
+
 Both pin `@fluixi/*` to the `next` dist-tag and set `jsxImportSource: "@fluixi/jsx"`.
 
 ## 🧱 Scaffolding pieces

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-fluixi",
-  "version": "0.1.0-alpha.8",
+  "version": "0.1.0-alpha.9",
   "license": "MIT",
   "description": "Scaffold a new Fluixi app — `npm create fluixi <dir>`.",
   "type": "module",

package/template-spa/vite.config.ts

@@ -2,5 +2,12 @@ import { defineConfig } from 'vite';
 import { fluixi } from '@fluixi/vite-plugin';
 
 export default defineConfig({
-  plugins: [fluixi()],
+  plugins: [
+    fluixi({
+      // Where a capitalised tag with no import in scope comes from. One pattern covers
+      // the whole folder, so a new component needs no config — `fluixi g component Card`
+      // and `<Card />` just works. Delete this if you'd rather import every component.
+      resolve: [{ match: /^([A-Z]\w+)$/, module: '/src/components/$1.tsx' }],
+    }),
+  ],
 });

package/template-spa-html/vite.config.ts

@@ -2,5 +2,12 @@ import { defineConfig } from 'vite';
 import { fluixi } from '@fluixi/vite-plugin';
 
 export default defineConfig({
-  plugins: [fluixi()],
+  plugins: [
+    fluixi({
+      // Where a capitalised tag with no import in scope comes from. One pattern covers
+      // the whole folder, so a new component needs no config — `fluixi g component Card`
+      // and `<Card />` just works. Delete this if you'd rather import every component.
+      resolve: [{ match: /^([A-Z]\w+)$/, module: '/src/components/$1.ts' }],
+    }),
+  ],
 });

package/template-ssr/fluixi.config.ts

@@ -3,6 +3,10 @@ import { nodeAdapter } from '@fluixi/start/adapter';
 
 export default defineConfig({
   port: 3000,
+  // Where a capitalised tag with no import in scope comes from. One pattern covers
+  // the whole folder, so a new component needs no config — `fluixi g component Card`
+  // and `<Card />` just works. Delete this if you'd rather import every component.
+  resolve: [{ match: /^([A-Z]\w+)$/, module: '/src/components/$1.tsx' }],
   // `pnpm start` runs a Node process from this directory, so the framework stays an
   // import rather than being copied into dist/server. Swap in a deploy adapter —
   // cloudflare, netlify, vercel — to get the layout that platform expects.

package/template-ssr-html/fluixi.config.ts

@@ -3,6 +3,10 @@ import { nodeAdapter } from '@fluixi/start/adapter';
 
 export default defineConfig({
   port: 3000,
+  // Where a capitalised tag with no import in scope comes from. One pattern covers
+  // the whole folder, so a new component needs no config — `fluixi g component Card`
+  // and `<Card />` just works. Delete this if you'd rather import every component.
+  resolve: [{ match: /^([A-Z]\w+)$/, module: '/src/components/$1.ts' }],
   // `pnpm start` runs a Node process from this directory, so the framework stays an
   // import rather than being copied into dist/server. Swap in a deploy adapter —
   // cloudflare, netlify, vercel — to get the layout that platform expects.