Free tools for production debugging.

The tools

• • parseCurrencyStart here
  • createOrderApp code
  • async POSTApp code
  • async Server.handleRequestDependency
  • process.processTicksAndRejectionsDependency

  Stack trace parser→

  Paste a stack trace from Node.js, a browser, Python, Java, Ruby, or Go. The parser separates your code from dependencies and marks the first frame to open.

• Example checks

  Result	Check
  Warn	Names arraySome tools include names for clearer function-level frames.
  Warn	sourcesContentOne or more source paths do not include embedded source content.
  Warn	Bundle footerThe minified bundle snippet does not include a sourceMappingURL footer.

  Source map validator→

  Paste a .map file and the last lines of its bundle. The validator checks the fields error tools need and whether the bundle points at this map.

• Example checks

  Result	Check
  Pass	ProtocolThe endpoint uses HTTPS or a local development HTTP host.
  Warn	Signal pathSome collectors append /v1/logs; direct exporters usually need the full path.
  Pass	Authentication headerThe header shape matches x-squasher-key or Authorization: Bearer.

  OTLP endpoint tester→

  Pick a signal, then paste the exporter's URL and headers. The tester checks the scheme, the /v1 path, the auth header, and the content type, and sends nothing.

• Example checks

  Result	Check
  Warn	Squasher drain pathExpected a path like /v1/drain/vercel/<project_id> for Squasher-managed drains.
  Pass	Payload JSONParsed a single log object.
  Warn	Secret redactionRedact tokens, headers, API keys, and customer data before pasting samples.

  Vercel log drain tester→

  Paste the drain URL and one redacted log entry. The tester checks the URL, the JSON shape, the fields you need, and secrets you forgot to remove.

Previews show each tool's real result for one of its examples.