Error Report: 2026-04-02 (232 errors in last 24h)

[claude]

Summary

Three significant issues emerge: API deployment timeouts require backend investigation, build failures indicate tailwind ESM/CommonJS conflicts during eject, and authentication timeout volumes remain elevated. User validation errors continue working correctly with appropriate messaging.

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

Errors requiring action

1. Tailwind config ESM/CommonJS module conflicts during build — CLI bug

Error code	None (unclassified)
Occurrences	9 (0 internal)
Users affected	7
Command	eject
Platforms	darwin, windows
PostHog	None (issue_id is null)
Existing issue	None
Recurring	No

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

Command failed with exit code 1: 'npm run build'

ReferenceError: module is not defined
    at file:///Users/<redacted>/base44-imports/egg-garden/tailwind.config.js:2:1

Stack trace: (build failures don't generate CLI stack traces since they occur in subprocess)

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

Root cause: Build command execution in eject workflow fails when user projects have tailwind.config.js files using CommonJS syntax in ESM contexts:

// packages/cli/src/cli/commands/project/eject.ts:164-168
await execa({ cwd: resolvedPath, shell: true })`${installCommand}`;

updateMessage("Building project...");
await execa({ cwd: resolvedPath, shell: true })`${buildCommand}`;

The error occurs when ejected projects have tailwind.config.js files with module.exports = { ... } syntax but Node.js treats them as ES modules. The CLI correctly executes the build command but doesn't handle or provide guidance for ESM/CommonJS module conflicts in user project configurations.

Suggested fix: In packages/cli/src/cli/commands/project/eject.ts:168, wrap build command execution with better error handling to detect module syntax conflicts and provide actionable error messages suggesting fixes like renaming tailwind.config.js to tailwind.config.cjs or updating syntax to ESM exports.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
API timeout during site deploy	15	10	site deploy	link

The CLI correctly sets a 180-second timeout in packages/cli/src/core/site/api.ts:26 but the backend /api/apps/<id>/deploy-dist endpoint is taking longer to process uploaded archives. This indicates backend performance issues, not CLI problems.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Project not found for eject	85	21	eject	link
No Base44 project in directory	36	17	functions list	link
App not configured	19	11	functions list	link
Authentication timed out	17	16	create	link
Project already linked	10	8	link	link
Invalid schema validation	8	3	auth push	link
Deno dependency missing	6	5	exec	link

INVALID_INPUT volume analysis: The 85 occurrences of "Project not found for eject" indicate users frequently provide non-existent project IDs. The CLI validation in packages/cli/src/cli/commands/project/eject.ts:57-68 correctly checks project existence and provides appropriate error messages.

CONFIG validation: CONFIG_NOT_FOUND and CONFIG_INVALID errors show users running commands outside Base44 projects or with missing .app.jsonc files. Error messages correctly guide users to run base44 create or base44 link.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Authentication timeout	3+ days	Referenced in #458, #457, #451	No dedicated issue
API timeout (site deploy)	New pattern	none	no
INVALID_INPUT (eject)	3+ days	Referenced in #458, #457, #451	No dedicated issue

Authentication timeout pattern: Authentication timeouts continue affecting 15-20 users daily across multiple commands (create, login, whoami). Previous reports (#458, #457, #451) show this as a consistent pattern.

API timeout (site deploy): New significant pattern affecting 15 occurrences. The backend API is taking longer than the 180-second CLI timeout to process site deployments.

Action items

1. [medium] packages/cli/src/cli/commands/project/eject.ts:168 — Add build error detection for ESM/CommonJS module conflicts and provide actionable guidance (rename config files to .cjs or update syntax)
2. [medium] Backend team should investigate site deployment API performance - 15 timeouts despite 180-second CLI timeout configuration
3. [low] Consider tracking authentication timeout pattern as dedicated issue since it's been recurring across 3+ daily reports affecting 15-20 users consistently