Error Report: 2026-04-13 (326 errors in last 24h)

[claude]

Summary

Network connectivity errors dominate with ECONNRESET failures affecting deploy operations. Most errors are expected user validation with appropriate CLI messaging. One template creation bug shows path corruption.

Metric	Value
Time range	last 24 hours
Total errors	326
CLI bugs	1
Backend issues	1
User errors (working as designed)	7
Unique users affected	89
Internal user occurrences	14

Errors requiring action

1. Path corruption in template creation causing ENOENT errors — CLI bug

Error code	None (unclassified)
Occurrences	6 (0 internal)
Users affected	6
Command	eject
Platforms	Windows
PostHog	None (issue_id null)
Existing issue	None
Recurring	New

Error: (from PostHog — the actual error message users see)

Failed to process template file "base44/app.jsonc.ejs": ENOENT: no such file or directory, mkdir 'C:\Users\<redacted>\Downloads\lonely-stars-ai (3)\lonely-stars-ai-3-lonelyheartz-date-a-pornC:\Users\<redacted>\OneDrive\Desktop\base44'

Stack trace: (only CLI stack trace frames)

at runCLI (packages/cli/src/cli/index.ts:59:4)
at Command.parseAsync (commander/lib/command.js:1243:4)

Root cause: Path corruption occurs during Windows path resolution in template creation. The error shows two paths incorrectly concatenated:

// packages/cli/src/core/project/template.ts:73-78
const destFilePath = join(destPath, file);
await copyFile(srcPath, destFilePath);
// Error handling wraps this with template file context:
throw new Error(`Failed to process template file "${file}": ${message}`);

The error shows paths like C:\Users\...\lonely-stars-ai-3-lonelyheartz-date-a-pornC:\Users\...\OneDrive\Desktop\base44 where directory paths get incorrectly merged on Windows systems, suggesting an issue with path resolution in the destPath variable.

Suggested fix: In packages/cli/src/core/project/template.ts:73, add Windows-specific path normalization and validation before calling join() to prevent path corruption during directory resolution.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Network connectivity (ECONNRESET, timeouts)	30	14	deploy	View

Network errors show various patterns:

• write ECONNRESET - TCP connection reset during requests
• fetch failed - General network failures
• Request timed out - API endpoint timeouts

These indicate server-side connectivity or timeout issues during deployment operations.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No Base44 project found	86	22	link, dev, functions deploy	View
--yes required in non-interactive mode	80	26	site deploy	View
Entity schema validation errors	50	12	entities push, deploy, dev, eject	Multiple PostHog links
Project already linked	23	10	link	View
App not configured	19	8	functions deploy	View
Deno dependency missing	7	6	exec	View
Authentication timeout	5	5	deploy	View

All user errors show appropriate validation patterns:

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/errors.ts:169 and packages/cli/src/core/project/config.ts:75, users running commands outside Base44 project directories get clear validation with guidance to run from directories with config.jsonc files.

INVALID_INPUT analysis: Various validation patterns including duplicate function names, missing required flags, and directory validation all provide clear error messaging.

SCHEMA_INVALID analysis: Entity file validation errors show specific validation failures with file paths and field-level error details.

Recurring errors

Based on previous daily reports, these errors have appeared multiple days:

Error	Days recurring	Existing issue	Tracked?
CONFIG_NOT_FOUND validation	5+ days	Referenced in #474, #473, #472	Yes (expected user error)
INVALID_INPUT validation	5+ days	Referenced in #474, #473, #472	Yes (expected user error)
Network connectivity errors	4+ days	Referenced in #474, #473	No
Path corruption (various commands)	4+ days	Referenced in #474, #473, #470, #467	Partially (different manifestations)

The path corruption issue manifests differently across commands but shows a consistent pattern of Windows path handling problems.

Action items

1. [medium] packages/cli/src/core/project/template.ts:73 — Add Windows-specific path validation and normalization before join() call to prevent path corruption during template file operations

The network connectivity errors (30 occurrences) are backend infrastructure issues requiring server-side investigation, not CLI changes.