create-foldkit-app 0.15.0 → 0.15.2

package/dist/index.js

@@ -1,9 +1,9 @@
 #!/usr/bin/env node
-import { NodeRuntime, NodeServices, NodeStdio } from '@effect/platform-node';
 import { Effect, Layer, Option, Schema } from 'effect';
 import { Command, Flag } from 'effect/unstable/cli';
 import { FetchHttpClient } from 'effect/unstable/http';
 import { createRequire } from 'node:module';
+import { NodeRuntime, NodeServices, NodeStdio } from '@effect/platform-node';
 import { create as create_ } from './commands/create.js';
 import { EXAMPLE_VALUES } from './examples.js';
 import { validateProjectName } from './validateName.js';

package/dist/utils/packages.js

@@ -9,7 +9,15 @@ const PackageJson = Schema.Struct({
     dependencies: StringRecord.pipe(Schema.withDecodingDefaultKey(Effect.succeed({}))),
     devDependencies: StringRecord.pipe(Schema.withDecodingDefaultKey(Effect.succeed({}))),
 });
-const formatDeps = (deps) => pipe(deps, Record.toEntries, Array.filter(([_, version]) => !version.includes('workspace:')), Array.map(([name, version]) => `${name}@${version}`));
+// NOTE: foldkit workspace packages an example may depend on that aren't
+// already installed at `latest` by the hardcoded commands below. They ship
+// from the same monorepo, so pin them to `latest` like `foldkit` itself.
+const PASS_THROUGH_WORKSPACE_PACKAGES = new Set([
+    '@foldkit/ui',
+    '@foldkit/devtools',
+]);
+const formatDeps = (deps) => pipe(deps, Record.toEntries, Array.filter(([name, version]) => !version.includes('workspace:') ||
+    PASS_THROUGH_WORKSPACE_PACKAGES.has(name)), Array.map(([name, version]) => version.includes('workspace:') ? `${name}@latest` : `${name}@${version}`));
 const fetchExampleDeps = (example) => Effect.gen(function* () {
     const client = yield* HttpClient.HttpClient;
     const url = `${GITHUB_RAW_BASE_URL}/${example}/package.json`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-foldkit-app",
-  "version": "0.15.0",
+  "version": "0.15.2",
   "description": "Create Foldkit applications",
   "type": "module",
   "main": "./dist/index.js",

package/templates/base/.prettierrc

@@ -5,7 +5,7 @@
   "trailingComma": "all",
   "printWidth": 80,
 
-  "importOrder": ["<THIRD_PARTY_MODULES>", "^[./]"],
+  "importOrder": ["<THIRD_PARTY_MODULES>", "^@", "^[./]"],
   "importOrderSeparation": true,
   "importOrderSortSpecifiers": true,
 

package/templates/base/AGENTS.md

@@ -72,7 +72,9 @@ Use uppercase section headers (`// MODEL`, `// MESSAGE`, `// INIT`, `// UPDATE`,
 
 ### Testing
 
-Test update functions with `foldkit/test`. Since update is pure, tests run without a runtime, DOM, or side effects. Use `Story.story` for update-level tests (send Messages, assert on Model and Commands) and `Scene.scene` for feature-level testing through the view with accessible locators. If the `repos/foldkit` subtree is available, study the `.story.test.ts` and `.scene.test.ts` files in `repos/foldkit/examples/`.
+Test update functions with `foldkit/test`. Since update is pure, tests run without a runtime, DOM, or side effects. Use `Story.story` for update-level tests (send Messages, assert on Model and Commands) and `Scene.scene` for feature-level testing through the view with accessible locators.
+
+Name each test file for its test style, beside the code under test: `story.test.ts` for the Story tests (which drive `update`) and `scene.test.ts` for the Scene tests (which drive the rendered view). The name describes how the test works, not a source file, so it stays correct whether `update` and `view` live in `main.ts` or in their own files. When one folder holds more than one test of a kind (sibling pages, component variants), prefix with the subject: `login.story.test.ts`. Scene tests always run from the root `update`/`view`, so a single root-level `scene.test.ts` is the right home even in a multi-page app. If the `repos/foldkit` subtree is available, study the `story.test.ts` and `scene.test.ts` files in `repos/foldkit/examples/`.
 
 ## Code Style
 

package/templates/base/vite.config.ts

@@ -1,6 +1,7 @@
+import { defineConfig } from 'vite'
+
 import { foldkit } from '@foldkit/vite-plugin'
 import tailwindcss from '@tailwindcss/vite'
-import { defineConfig } from 'vite'
 
 export default defineConfig({
   plugins: [tailwindcss(), foldkit({ devToolsMcpPort: 9988 })],