Files
WRNexusJS/packages
ClintchizandClaude Opus 5 cc464afdfb 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>
2026-09-18 12:27:32 +05:30
..
2026-08-11 13:40:03 +05:30
2026-08-11 13:40:03 +05:30
2026-08-11 13:40:03 +05:30
2026-08-11 13:40:03 +05:30
2026-08-11 13:40:03 +05:30
2026-08-11 13:40:03 +05:30
2026-08-11 13:40:03 +05:30
2026-08-11 13:40:03 +05:30