Files
sase.tr/.agents/skills/next-best-practices/runtime-selection.md
Sase Dev 996d614d50 feat: admin user creation, Vite migration, dialog fix, pl24 integration
- Add POST /admin/users endpoint with password hashing and role support
- Add user creation dialog to admin users page
- Migrate web from Next.js to Vite + TanStack Router
- Fix Dialog component positioning for Tailwind CSS v4
- Add @source directive for @sase/ui package scanning
- Add pl24 integration parsers and vehicle decode flow
- Backup old Next.js app to apps/web-nj

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-12 14:24:58 +00:00

985 B

Runtime Selection

Use Node.js Runtime by Default

Use the default Node.js runtime for new routes and pages. Only use Edge runtime if the project already uses it or there's a specific requirement.

// Good: Default - no runtime config needed (uses Node.js)
export default function Page() { ... }

// Caution: Only if already used in project or specifically required
export const runtime = 'edge'

When to Use Each

Node.js Runtime (Default)

  • Full Node.js API support
  • File system access (fs)
  • Full crypto support
  • Database connections
  • Most npm packages work

Edge Runtime

  • Only for specific edge-location latency requirements
  • Limited API (no fs, limited crypto)
  • Smaller cold start
  • Geographic distribution needs

Detection

Before adding runtime = 'edge', check:

  1. Does the project already use Edge runtime?
  2. Is there a specific latency requirement?
  3. Are all dependencies Edge-compatible?

If unsure, use Node.js runtime.