chore(apps): swap default runtime backend from deno to node
Merged
D-
3mo ago+16+16+01234567890123456789-10-10-01234567890123456789
- feat(apps-engine): default runtime backend to node
- ci: repurpose dedicated apps runtime job to test deno instead of node
Proposed changes (including videos or screenshots)
Issue(s)
Steps to test or reproduce
Further comments
Summary by CodeRabbit
- New Features
- The default Apps runtime backend is now Node.js.
- Deno is still supported by setting
APPS_ENGINE_RUNTIME_BACKEND='deno'.
- Bug Fixes
- Updated runtime selection so the configured backend is consistently honored.
- Tests
- CI and E2E coverage was updated to run the Apps-based API tests against the Deno runtime when applicable.