Give the generated server module the workspace's own @wrnexus/core
The execution tests wrote the generated module to an OS tmpdir and junctioned @wrnexus/core in beside it. On Windows that tmpdir sits on another volume, and the junction resolved to a second copy of the package: the request context lives in an AsyncLocalStorage inside core, so the module read a store the test could never populate and all six execution tests failed with "needs a request context". The module is now written inside the repo, where resolution walks up to this workspace's node_modules and finds the same instance the test holds. That identity is the whole point, so the junction is gone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a154e6c26e
commit
cc464afdfb
2 files changed
+15
-22
No files matched your search
@@ -28,3 +28,6 @@ tsconfig.focus.json
|
||||
|
||||
# Subagent-driven-development scratch (ledger, briefs, review packages)
|
||||
.superpowers/
|
||||
|
||||
# Scratch modules written by tests that must resolve this workspace.
|
||||
.tmp-tests/
|
||||
Reference in new issue
Block a user