aws-samples / aws-samples/agents4energy
deploy fix
- Dominant language
- TypeScript
- Stars
- 48
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
## log
Building Next.js app…
> web@0.1.0 build /home/runner/work/agents4energy/agents4energy/web
> next build
⚠ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
▲ Next.js 16.2.7 (Turbopack)
Creating an optimized production build ...
✓ Compiled successfully in 18.3s
Running TypeScript ...
Failed to type check.
./lib/harness-agent.ts:289:27
Type error: Property 'timestamp' does not exist on type 'StoredEvent'.
287 | // (oldest first) before converting to AG-UI messages to ensure correct display order.
288 | const sorted = all.sort((a, b) => {
> 289 | const at = new Date(a.timestamp).getTime();
| ^
290 | const bt = new Date(b.timestamp).getTime();
291 | return at - bt;
292 | });
Next.js build worker exited with code: 1 and signal: null
/home/runner/work/agents4energy/agents4energy/web:
ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL web@0.1.0 build: `next build`
Exit status 1
Contributor guide
Research direction
Start at web/lib/harness-agent.ts:289 and inspect the StoredEvent type and the surrounding event-sorting code. Run the web package's `next build` command to reproduce the TypeScript error; done means the type check and production build complete successfully without the timestamp error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, typescript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100