You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I am experiencing an issue with micro-agent where it hangs with a flashing cursor and does not proceed. Below are the detailed steps and outputs from the troubleshooting process.
Steps to Reproduce:
Installed Node.js v22.4.1 and npm v10.8.1.
Installed micro-agent using npm install -g @builder.io/micro-agent.
Ran micro-agent with debug logging enabled.
Observed deprecation warning for the punycode module and the program hanging without further progress.
Commands and Outputs:
node -v: v22.4.1
(node:24024) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
(Use node --trace-deprecation ... to show where the warning was created)
Module Not Found Error:
C:\Users\cam[eval]
at Module._resolveFilename (node:internal/modules/cjs/loader:1219:15)
at Module._load (node:internal/modules/cjs/loader:1045:27)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:215:24)
at Module.require (node:internal/modules/cjs/loader:1304:12)
at require (node:internal/modules/helpers:123:16)
at [eval]:1:1
at runScriptInThisContext (node:internal/vm:209:10)
at node:internal/process/execution:118:14
at [eval]-wrapper:6:24 {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'C:\Users\cam\[eval]' ]
}
Node.js v22.4.1
Additional Information:
The issue occurs in both PowerShell and Command Prompt.
Network connectivity is verified.
Running node --trace-deprecation -e "require('@builder.io/micro-agent')" results in a module not found error.
Environment:
Windows 11 [Version 10.0.22631.3810]
Debug and environment variables set:
DEBUG: micro-agent:*
NODE_NO_WARNINGS: 1
The text was updated successfully, but these errors were encountered:
boogieking
changed the title
Micro-Agent Hangs with Flashing Cursor and Deprecation Warnings on Windows 11
Micro-Agent Hangs with Flashing Cursor
Jul 10, 2024
Description:
I am experiencing an issue with micro-agent where it hangs with a flashing cursor and does not proceed. Below are the detailed steps and outputs from the troubleshooting process.
Steps to Reproduce:
Installed Node.js v22.4.1 and npm v10.8.1.
Installed micro-agent using npm install -g @builder.io/micro-agent.
Ran micro-agent with debug logging enabled.
Observed deprecation warning for the punycode module and the program hanging without further progress.
Commands and Outputs:
node -v: v22.4.1
npm -v: 10.8.1
npm list -g --depth=0:
C:\Users\cam\AppData\Roaming\nvm\v22.4.1
+-- @builder.io/[email protected]
+-- [email protected]
`-- [email protected]
Deprecation Warning:
(node:24024) [DEP0040] DeprecationWarning: The
punycode
module is deprecated. Please use a userland alternative instead.(Use
node --trace-deprecation ...
to show where the warning was created)Module Not Found Error:
node:internal/modules/cjs/loader:1222
throw err;
^
Error: Cannot find module '@builder.io/micro-agent'
Require stack:
at Module._resolveFilename (node:internal/modules/cjs/loader:1219:15)
at Module._load (node:internal/modules/cjs/loader:1045:27)
at TracingChannel.traceSync (node:diagnostics_channel:315:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:215:24)
at Module.require (node:internal/modules/cjs/loader:1304:12)
at require (node:internal/modules/helpers:123:16)
at [eval]:1:1
at runScriptInThisContext (node:internal/vm:209:10)
at node:internal/process/execution:118:14
at [eval]-wrapper:6:24 {
code: 'MODULE_NOT_FOUND',
requireStack: [ 'C:\Users\cam\[eval]' ]
}
Node.js v22.4.1
Additional Information:
The issue occurs in both PowerShell and Command Prompt.
Network connectivity is verified.
Running node --trace-deprecation -e "require('@builder.io/micro-agent')" results in a module not found error.
Environment:
Windows 11 [Version 10.0.22631.3810]
Debug and environment variables set:
DEBUG: micro-agent:*
NODE_NO_WARNINGS: 1
The text was updated successfully, but these errors were encountered: