create-claude-workspace 1.1.98 → 1.1.100
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -497,6 +497,11 @@ export function runClaude(opts, log, runOpts = {}) {
|
|
|
497
497
|
detectErrorSignals(event);
|
|
498
498
|
// Track pending tool calls — tool_use in assistant, tool_result in user
|
|
499
499
|
if (event.type === 'assistant') {
|
|
500
|
+
// Reset resultReceived — Claude is still actively working, so any earlier
|
|
501
|
+
// result event (e.g. from a sub-agent with --include-partial-messages) was
|
|
502
|
+
// not the final one. Without this, postResultTimeout (30s) kills the process
|
|
503
|
+
// while Claude is thinking before its next tool call.
|
|
504
|
+
resultReceived = false;
|
|
500
505
|
const blocks = getContentBlocks(event);
|
|
501
506
|
if (blocks) {
|
|
502
507
|
for (const block of blocks) {
|
|
@@ -124,7 +124,7 @@ List of all files to create/modify, with full paths.
|
|
|
124
124
|
- **NEVER use `nx:run-commands` executor** in project.json targets. Always use the proper built-in Nx executor for each target type:
|
|
125
125
|
- serve: `@nx/js:node` (Node.js backend)
|
|
126
126
|
- build: `@nx/js:tsc`, `@nx/vite:build`, `@nx/esbuild:esbuild`
|
|
127
|
-
- test: `@nx/
|
|
127
|
+
- test: `@nx/vitest:test` (Vitest), `@nx/jest:jest`
|
|
128
128
|
- lint: `@nx/eslint:lint`
|
|
129
129
|
- `nx:run-commands` is an escape hatch, not a default. Built-in executors handle watch mode, HMR, process management, and Nx dependency graph integration.
|
|
130
130
|
|
|
@@ -149,7 +149,7 @@ Read `.claude/profiles/frontend.md` for the framework-specific review checklist.
|
|
|
149
149
|
- Stylelint — no hardcoded colors or sizes in SCSS (must use theme tokens from frontend profile)
|
|
150
150
|
- New libraries MUST be created via generators (`nx generate` or framework CLI), not manually — flag if config files contain hand-written targets for standard operations (build, test, lint)
|
|
151
151
|
- **No manual build tool configs**: Flag CRITICAL if `tsup.config.ts`, `esbuild.config.js`, `rollup.config.js`, `webpack.config.js` are added manually. Nx generators handle build configuration — internal libs don't need a build step, publishable libs get `--bundler` from the generator
|
|
152
|
-
- **No `nx:run-commands` executor**: Flag CRITICAL if any project.json target uses `nx:run-commands` for standard operations (serve, build, test, lint). Must use built-in executors (`@nx/js:node`, `@nx/vite:build`, `@nx/eslint:lint`, etc.). `nx:run-commands` is an escape hatch, not a default.
|
|
152
|
+
- **No `nx:run-commands` executor**: Flag CRITICAL if any project.json target uses `nx:run-commands` for standard operations (serve, build, test, lint). Must use built-in executors (`@nx/js:node`, `@nx/vite:build`, `@nx/vitest:test`, `@nx/eslint:lint`, etc.). `nx:run-commands` is an escape hatch, not a default.
|
|
153
153
|
|
|
154
154
|
## Output Format
|
|
155
155
|
|
|
@@ -27,7 +27,7 @@ Before writing ANY test, detect which test framework the project uses:
|
|
|
27
27
|
1. Check for `vitest.config.ts` or `vitest.config.js` -> **Vitest**
|
|
28
28
|
2. Check for `jest.config.ts` or `jest.config.js` -> **Jest**
|
|
29
29
|
3. Check `package.json` devDependencies for `vitest` or `jest`
|
|
30
|
-
4. Check `nx.json` or `project.json` for test executor (`@nx/
|
|
30
|
+
4. Check `nx.json` or `project.json` for test executor (`@nx/vitest:test` = Vitest, `@nx/jest:jest` = Jest)
|
|
31
31
|
5. If ambiguous, check existing `.spec.ts` files for import patterns (`from 'vitest'` vs `// no import = Jest globals`)
|
|
32
32
|
|
|
33
33
|
**Adapt your output accordingly:**
|