-
-
Notifications
You must be signed in to change notification settings - Fork 872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use stderr instead console.log #860
Comments
Yeah this is a good point. Have you seen dotenvx? It does this correctly. Can you also speak to MCP more? Are you using dotenv as an MCP server somehow? |
I will take a look at dotenvx.
I have a node.js application that runs as an MCP. When using the stdio transport, any console.log output will be interpreted in the MCP transports which leads to some warnings about incorrect messages. |
i'm removing meanwhile, dotenvx will support more controlled log levels: ![]() |
It would be nice to avoid writing to console.log for debugging messages. Since MCP is using stdio, those messages generate errors in the protocols.
dotenv/lib/main.js
Line 93 in 59d9e87
The text was updated successfully, but these errors were encountered: