Fix Render deploy: add .js extensions to ES module imports

[Copilot]

This PR fixes the Render deployment issue where the service fails to start with ERR_MODULE_NOT_FOUND errors.

Problem

The deployment was failing with:

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/opt/render/project/src/dist/hono/app' imported from /opt/render/project/src/dist/hono/index.js

Root Cause

When using ES modules ("type": "module" in package.json), Node.js requires explicit file extensions for relative imports. The TypeScript source files were using imports like:

import { app, injectWebSocket } from "./app";

But Node.js needs:

import { app, injectWebSocket } from "./app.js";

Solution

Updated all relative imports in TypeScript files to include explicit .js extensions:

• hono/index.ts: "./app" → "./app.js"
• hono/app.tsx: Updated all route imports to use .js extensions
• hono/routes/index.tsx: "../components/ChatPage" → "../components/ChatPage.js"
• All test files updated for consistency

Changes Made

• ✅ Fixed 9 TypeScript files with relative imports
• ✅ Added deployment test to validate ES module compatibility
• ✅ No changes needed to package.json or render.yaml

Validation

• Build completes successfully: pnpm run build ✅
• Production server starts without errors: pnpm run start:prod ✅
• All endpoints work correctly (health check, main page) ✅
• All existing tests continue to pass ✅
• New deployment tests validate import resolution ✅

The service now starts successfully and is ready for Render deployment.

Fixes #22.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mahata]

@copilot Fix CI in GitHub Actions.

[Copilot]

@copilot Fix CI in GitHub Actions.

Fixed the CI issue - it was a Biome linting error due to a missing newline at the end of the deployment.test.ts file. All CI steps now pass: tests ✅, linting ✅, build ✅. Commit 622c273