Getting Support

Self-service resources

Before contacting support, check:

• Common errors — most frequent issues and fixes.
• Compile failures — reading and diagnosing compiler output.
• Not supported — known unsupported features.
• GitHub issues — search for your error message or package name.

Contacting support

Email [email protected]. Response times:

Plan	First response
Free	5 business days
Pro	2 business days
Enterprise	4 hours (business hours)

What to include in a bug report

The faster you give us the details, the faster we can help. Include:

For compile failures

• Job ID — visible in the compile.queued message and in the dashboard. Format: job_...
• Entry point — the file you passed to pure build
• CLI version — output of pure --version
• Compile log — either the CLI output or the .pure_out_<name>/compile.log file
• Minimal reproduction — the smallest TypeScript/JavaScript file that triggers the failure. Remove all unrelated code.

For runtime crashes

• The binary — attach the compiled binary
• The source — attach the source file(s)
• Steps to reproduce — the exact command and input that causes the crash
• Error output — the full stderr output including any signal information

For API or registry issues

• Request details — the WebSocket message sequence or the HTTP request that fails
• Error message and code — from the compile.error or auth.error response
• Timestamp — so we can look up server-side logs (UTC preferred)

Feature requests

Open an issue on GitHub with the label enhancement. Describe the use case, not just the feature — it helps us prioritize.

Status page

Check status.pure.dev for ongoing incidents and scheduled maintenance. Subscribe to receive email alerts.