cnw-stats-local-server

You can intercept CNW or NX telemetry requests by running a local Go HTTP server that captures all traffic sent to NX_CLOUD_API. It logs the method, URL, headers, and body to stdout and a log file while responding 200 to every request.

Redirecting NX_CLOUD_API to a local capture server is the best way to inspect create-nx-workspace analytics without affecting production. It intercepts telemetry payloads for observation and safely returns a 200 response so CNW proceeds normally.

You can redirect NX_CLOUD_API to a local server by running the Go HTTP server with `go run . -port 8765 -log cnw-log-server.log` in the tools directory, then pointing your NX_CLOUD_API environment variable to the local server address.

Intercepting NX init telemetry with this approach requires no external dependencies, only a standard Go environment. The included HTTP server runs standalone to capture requests and log telemetry data locally without needing additional tools.

Yes, you can use a local HTTP server to test CNW telemetry without breaking the workspace creation flow. The server responds 200 to every intercepted request, ensuring CNW and nx init proceed normally after logging the traffic.