npm 0.2.0 still ships the unfixed build (console.log "Starting server" breaks stdio)

[randiri100]

Summary

The console.log("Starting server") → stdout bug from #9 is fixed in the repo source (index.ts and the committed dist/index.js both use console.error), and #9 was closed. However, the fix was never published to npm — the latest published version, @isaacphi/mcp-gdrive@0.2.0, still ships the broken build.

This was already pointed out in a comment on the closed #9, but it doesn't seem to have been picked up, so filing a fresh, focused issue.

Verification

$ npm view @isaacphi/mcp-gdrive version
0.2.0

$ npm pack @isaacphi/mcp-gdrive@0.2.0
$ grep -n "Starting server" package/dist/index.js
101:        console.log("Starting server");      # <-- stdout, still broken

Meanwhile the repo HEAD is correct:

dist/index.js:102:    console.error("Starting server");
index.ts:131:         console.error("Starting server");

Impact

Any MCP client that speaks JSON-RPC over stdio (Claude Desktop, Claude Code, custom gateways, etc.) installing via npx/npm gets the stale 0.2.0 build. On every startup the server writes a non-JSON line Starting server to stdout, which the client tries to parse as a JSON-RPC message and fails:

Unexpected token 'S', "Starting server" is not valid JSON

The server still works (the error is non-fatal), but it logs a parse error / traceback on every launch. The only workaround for users is to manually patch dist/index.js in their global install, which is lost on every reinstall.

Request

Please cut a new release (e.g. 0.2.1) and publish it to npm so the already-merged fix actually reaches users. No code change needed — just a rebuild + npm publish from current main.

Thanks for maintaining this!