Repository navigation
Root entry (require/import 'lean-agentic') fails: dist/index.* loads ../wasm/ which is never published #5
Description
Since at least 0.3.2 (and still in 0.3.3), the package root entry point cannot be loaded:
$ node -e 'require("lean-agentic")'
Error: Cannot find module '../wasm/leanr_wasm.js'
$ node --input-type=module -e 'import "lean-agentic"'
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '.../node_modules/lean-agentic/wasm/leanr_wasm.js'
dist/index.js and dist/index.mjs import ../wasm/leanr_wasm.js, which is the wasm-pack --target bundler output. That wasm/ directory is not in the published tarball, and a bundler-target build would not load in plain Node anyway. lean-agentic/node, the CLI and the MCP server work because they use wasm-node/.
Possible fixes: point the Node conditions of the . export at dist/node.*, or publish a working wasm/ build.
Separately, dist/node.js writes Initializing Lean-Agentic WASM... (and createIdentity logs) to stdout. That pollutes the MCP stdio JSON-RPC stream and should go to stderr.
🤖 Generated with claude-flow
Activity
lean-agentic 0.3.4: working root entry point, quiet MCP stdout (#5) (#6)
ruvnet commentedon Nov 6, 2026
Fixed in #6 and released as lean-agentic@0.3.4 (now
latest).I installed 0.3.4 from the registry into a fresh project and checked it:
requireandimportwork forlean-agenticandlean-agentic/node, andimportworks forlean-agentic/webandlean-agentic/package.json. None of them print anything to stdout. (import "lean-agentic/node"was also broken in 0.3.3:dist/node.mjswas CommonJS.)lean-agentic/node, plusinit(). Browsers uselean-agentic/web.LEAN_AGENTIC_DEBUG=1orsetDebug(true)) they go to stderr.lean-agentic mcp start, which never started the server in 0.3.3. Afterinitialize,notifications/initializedand twotools/calls, stdout holds only the three JSON-RPC responses.--versionanddemowork..wasmis 2,064 bytes smaller (logging is now behind a flag), and thedist/*.mjsfiles are now small ESM wrappers instead of copies of the CommonJS code.b05e762b).CI now runs the same check (
scripts/check-package.mjs) against the packed tarball on every PR.Still open and out of scope here:
benchmarkEquality()throwsunreachablein WASM because it usesstd::time::Instant. The README'sAgentIdentity/SignedProofexample uses symbols the npm package doesn't export.initializereportscapabilitiesas booleans rather than objects.🤖 Generated with claude-flow