create-hollware 0.3.0 → 0.5.0

package/template/tsconfig.json

@@ -0,0 +1,34 @@
+{
+  "compilerOptions": {
+    "target": "esnext",
+    "lib": [
+      "es2024"
+    ],
+    "module": "esnext",
+    "moduleResolution": "bundler",
+    "moduleDetection": "force",
+    "strict": true,
+    "noUncheckedIndexedAccess": true,
+    "noImplicitOverride": true,
+    "noFallthroughCasesInSwitch": true,
+    "noUnusedLocals": true,
+    "noUnusedParameters": true,
+    "verbatimModuleSyntax": true,
+    "isolatedModules": true,
+    "erasableSyntaxOnly": true,
+    "allowImportingTsExtensions": true,
+    "resolveJsonModule": true,
+    "skipLibCheck": true,
+    "noEmit": true,
+    "types": [
+      "./worker-configuration.d.ts",
+      "@cloudflare/vitest-plugin/types"
+    ]
+  },
+  "include": [
+    "worker-configuration.d.ts",
+    "hollware.config.ts",
+    "src",
+    "test"
+  ]
+}

package/template/vite.config.ts

@@ -0,0 +1,18 @@
+import { cloudflare } from '@cloudflare/vite-plugin'
+import { adminAssets } from '@hollware/admin'
+import { defineConfig } from 'vite-plus'
+
+export default defineConfig({
+  plugins: [cloudflare()],
+  // The admin's built files: served at /admin/ in development, and copied into the build, where
+  // the Worker's static assets hold them.
+  publicDir: adminAssets(),
+  // Hollware's own port, not Vite's default 5173, which the frontend next to it usually takes.
+  // It must stay the port of HOLLWARE_PUBLIC_URL in wrangler.jsonc: with strictPort, a port in
+  // use fails instead of moving to one the Host check would refuse.
+  server: { port: 5199, strictPort: true },
+  build: {
+    // What you deploy is what the size budget of Hollware measures: minified.
+    minify: true,
+  },
+})

package/template/vitest.config.ts

@@ -0,0 +1,38 @@
+import { cloudflareTest, readD1Migrations } from '@cloudflare/vitest-plugin'
+import { defineConfig } from 'vite-plus'
+import { unstable_readConfig as readWranglerConfig } from 'wrangler'
+
+// The test database gets the migrations that wrangler.jsonc points at, so the tests cannot drift
+// from what `wrangler d1 migrations apply` would run.
+const wranglerConfig = readWranglerConfig({ config: `${import.meta.dirname}/wrangler.jsonc` })
+const migrationsDir: unknown = wranglerConfig.d1_databases.find(
+  (database: { binding: string }) => database.binding === 'DB',
+)?.migrations_dir
+if (typeof migrationsDir !== 'string') {
+  throw new Error('wrangler.jsonc must declare the D1 binding DB with a migrations_dir')
+}
+
+export default defineConfig({
+  plugins: [
+    cloudflareTest(async () => ({
+      wrangler: { configPath: './wrangler.jsonc' },
+      miniflare: {
+        // Read here in Node and applied inside workerd by the setup file.
+        bindings: {
+          TEST_MIGRATIONS: await readD1Migrations({
+            projectPath: import.meta.dirname,
+            migrationsDir,
+          }),
+        },
+      },
+    })),
+  ],
+  test: {
+    name: 'starter:workerd',
+    include: ['test/**/*.workerd.test.ts'],
+    setupFiles: ['test/apply-migrations.ts'],
+    // The default, kept explicit: @cloudflare/vitest-plugin cannot read Vitest 5's module cache from
+    // workerd ("no such file or directory, readAll .vitest-cache/..."), cloudflare/workers-sdk#15618.
+    fsModuleCache: false,
+  },
+})