create-zerotal 1.0.2 → 1.0.4

package/CHANGELOG.md

@@ -8,6 +8,25 @@ follows the Zerotal monorepo's unified versioning.
 
 ## [Unreleased]
 
+## [1.0.4] — 2026-08-07
+
+### Fixed
+
+- **The Flow starter rendered unstyled.** Its layout linked `/app.css` while the
+  asset build writes `public/css/app.css`, so every page loaded with a 404 for
+  the stylesheet — a one-segment path mismatch that looks like a CSS problem.
+  A test now asserts the rendered page names the path the build produces.
+- The Flow starter also declares a favicon, so a fresh `serve --dev` no longer
+  logs a 404 for `/favicon.ico` on every page load.
+
+## [1.0.3] — 2026-08-07
+
+### Changed
+
+- Re-released from a rebuilt repository so the build provenance resolves. The
+  1.0.2 attestation names a repository that was renamed away, which leaves the
+  signature valid but the trace back to source dangling. No code changed.
+
 ## [1.0.2] — 2026-08-06
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-zerotal",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "Create a new Zerotal application",
   "license": "MIT",
   "maturity": "stable",

package/src/scaffold.ts

@@ -13,7 +13,7 @@ export type Template = 'minimal' | 'api' | 'admin' | 'flow' | 'react' | 'vue';
 // "^1.1.0" found for specifier "zerotal"` — the first thing anyone trying the
 // framework saw. `scaffold.test.ts` now asserts the two agree, so CI fails rather
 // than the user's install.
-export const ZT_VERSION = '^1.0.2';
+export const ZT_VERSION = '^1.0.4';
 
 export interface ScaffoldOptions {
   name:     string;

package/templates/flow/app/flow/layouts/app.tsx

@@ -18,13 +18,17 @@ const GUEST_NAV = [
 ];
 
 export class AppLayout extends Layout {
-  // Built by `bun zt serve` from resources/css/app.css (Tailwind) → public/app.css.
+  // Built by `bun zt serve` from resources/css/app.css (Tailwind). The bundler
+  // mirrors the source layout under the asset outDir, so it lands at
+  // public/css/app.css and is served from /css/app.css — not /app.css.
+  //
   // A getter (not a static field) so asset() re-runs per request and picks up
   // the latest ?v= cache-busting token after a dev rebuild.
   static override get head(): string {
     return `
   <meta name="viewport" content="width=device-width, initial-scale=1">
-  <link rel="stylesheet" href="${asset("/app.css")}">
+  <link rel="icon" href="/zt.svg" type="image/svg+xml">
+  <link rel="stylesheet" href="${asset("/css/app.css")}">
   `;
   }
 

package/templates/flow/tests/smoke.test.ts

@@ -74,3 +74,17 @@ describe('auth', () => {
     expect(res.status).toBe(302);
   });
 });
+
+/**
+ * The stylesheet link has to name the path the asset build actually writes.
+ * It shipped pointing at /app.css while the build produced public/css/app.css,
+ * so every page rendered unstyled with a 404 in the log — a failure that looks
+ * like a CSS problem and is really a one-segment path mismatch.
+ */
+describe('assets', () => {
+  test('links the stylesheet where the build writes it', async () => {
+    const res = await app.get('/');
+
+    res.assertSee('/css/app.css');
+  });
+});