@mars-stack/cli 8.0.9 → 8.0.11

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mars-stack/cli",
-  "version": "8.0.9",
+  "version": "8.0.11",
   "description": "MARS CLI: scaffold, configure, and maintain SaaS apps",
   "license": "MIT",
   "repository": {

package/template/e2e-kitchen-sink/kitchen-sink-catalog.spec.ts

@@ -29,7 +29,8 @@ test.describe('Kitchen-sink CLI catalog (MARS-041)', () => {
 
   test('blog: listing page shows Blog heading', async ({ page }) => {
     await page.goto('/blog');
-    await expect(page.getByRole('heading', { name: 'Blog' })).toBeVisible();
+    // Substring match would also hit post titles like "Welcome to the Blog".
+    await expect(page.getByRole('heading', { name: 'Blog', exact: true })).toBeVisible();
   });
 
   test('dark-mode: theme toggle is present and clickable', async ({ page }) => {

package/template/scripts/seed.ts

@@ -1,7 +1,8 @@
-// Relative import: `prisma db seed` runs this file with `tsx`. The `@db` tsconfig alias
-// is not a valid Node package name (ERR_INVALID_MODULE_SPECIFIER). Omit `.js` so tsx
-// resolves Prisma’s emitted `client.ts` (there is no standalone `client.js` on disk).
-import { PrismaClient } from '../prisma/generated/prisma/client';
+// `prisma db seed` / Playwright webServer run this file with `tsx` under Node ESM.
+// The `@db` alias works for Next/tsc but is not a valid package specifier for Node's
+// resolver, so seed must import the generated client via a relative path (tsx resolves
+// `client.js` to the emitted `client.ts`).
+import { PrismaClient } from '../prisma/generated/prisma/client.js';
 import { PrismaPg } from '@prisma/adapter-pg';
 import { hashPassword } from '@mars-stack/core/auth/password-hash';