allow express app for consumption APIs in moose project

[onelesd]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
framework-docs	Ready	Preview	Comment	Oct 9, 2025 9:11pm

[Copilot]

Pull Request Overview

This PR adds support for Express applications in Moose projects as consumption APIs through a "Bring Your Own Framework" (BYOF) system. It allows developers to create Express apps alongside existing Moose APIs, with automatic detection, loading, and route collision handling.

Key changes:

• New BYOF system that automatically detects and loads Express apps with createApp functions
• Framework adapter pattern supporting Express (with extensibility for other frameworks)
• Route collision detection between custom Express apps and existing Moose API instances
• New TypeScript Express template demonstrating the integration

Reviewed Changes

Copilot reviewed 18 out of 18 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
templates/typescript-express/*	Complete new template showing Express integration with Moose, including models, transforms, views, workflows, and Express API
packages/ts-moose-lib/src/consumption-apis/byof-*.ts	Core BYOF system implementation with app loading, framework adapters, and collision detection
packages/ts-moose-lib/src/consumption-apis/runner.ts	Integration of BYOF system into existing API server with combined request handler
packages/ts-moose-lib/src/consumption-apis/moose-logger.ts	Express middleware for consistent logging format
packages/ts-moose-lib/src/index.ts	Export of moose logger for template usage

Comments suppressed due to low confidence (1)

packages/ts-moose-lib/src/consumption-apis/byof-adapter.ts:1

• Similar to the previous comment, extensive use of any types reduces type safety. Consider using proper method signatures from Node.js HTTP types.

import type http from "http";

[Copilot]

The use of any types reduces type safety. Consider using proper TypeScript method signatures for res.end and res.writeHead instead of casting to any.

Suggested change

	res.end = ((...args: any[]) => {
	responseSent = true;
	return (originalEnd as any)(...args);
	}) as any;
	res.writeHead = ((...args: any[]) => {
	responseSent = true;
	return (originalWriteHead as any)(...args);
	}) as any;
	res.end = function (
	this: typeof res,
	...args: Parameters<typeof res.end>
	): ReturnType<typeof res.end> {
	responseSent = true;
	return originalEnd(...args);
	};
	res.writeHead = function (
	this: typeof res,
	...args: Parameters<typeof res.writeHead>
	): ReturnType<typeof res.writeHead> {
	responseSent = true;
	return originalWriteHead(...args);
	};