New framework package

[fredericbarthelet]

Skybridge currently exposes 2 entry points: skybridge/web and skybridge/server.
One working ChatGPT app orchestrating both those packages is implemented in https://github.com/alpic-ai/apps-sdk-template.
This discussion aims at defining the scope of a new skybridge/core entry point dedicated to the orchestration of a working app.

Core package is a single developer interface that enable building ChatGPT app (and MCP app in the future).

Objectives of the new package:

• minimal boilerplate needed
• no platform-specific development requirements (you don't need to develop one MCP App, one ChatGPT App, ...)
• single package payload (our current template is too complexe and gives the impression multiple hosting solutions might be required)

This core package target developper that start a new app from scratch, no migration path will be provided or even supported.

The following discussion details (but is not limited to) proposal of implementation regarding the following points:

• file-based convention or explicit registration for tools, resources, prompts, widgets
• routing engine (express, koa, hono, fastify or anything framework agnostic) -> ideally, support replacing the default engine with any interface-compatible engine?
• bundler selection (only if we do file-based convention)
• configuration file via static or programmatic definition

There is a path to this destination from our current template that involves less work: merge front/back packages in a single package and replace the convention based template rendering in resource with configuration.

[fredericbarthelet]

File-based vs explicit registration

Current market state

TL;DR: Most fullstack frameworks implement file based configuration. Most server-side only frameworks use explicit registration.

Framework	GitHub Repository	Stars (⭐)	Used By	Latest Release	Category
Next.js	vercel/next.js	136K	5M	Today	File-based (Meta)
NestJS	nestjs/nest	73.6K	670K	Today	Decorator-based
Strapi	strapi/strapi	70.5K	28.3K	Today	Config-driven
Express	expressjs/express	68.2K	32.8M	Today	Explicit
Nuxt.js	nuxt/nuxt	59K	400K	Today	File-based (Meta)
Meteor	meteor/meteor	44.8K	N/A	Today	Convention
Koa	koajs/koa	35.7K	503K	Today	Explicit
Fastify	fastify/fastify	35.1K	169K	Today	Explicit
Remix	remix-run/remix	32.0K	N/A	Today	File-based (Meta)
Hono	honojs/hono	27.3K	62.4K	Today	Explicit
Sails.js	balderdashy/sails	22.9K	27.5K	May, 2024	Convention
SvelteKit	sveltejs/kit	20K	N/A	Today	File-based (Meta)
AdonisJS	adonisjs/core	18.4K	N/A	Today	Convention
Redwood.js	redwoodjs/redwood	17.6K	N/A	Today	Convention (Meta)
Feathers	feathersjs/feathers	15.2K	N/A	Today	Explicit
Hapi	hapijs/hapi	14.7K	N/A	Feb, 2023	Config-driven
LoopBack	strongloop/loopback	13.2K	N/A	Mar 2021	Decorator-based
SolidStart	solidjs/solid-start	~5K	N/A	Today	File-based (Meta)
Tsed	tsedio/tsed	~3K	N/A	Today	Decorator-based
Analog	analogjs/analog	~2K	N/A	Today	File-based (Meta)

Category 1: Explicit Registration (Low-level HTTP frameworks)

These frameworks require developers to manually register routes, controllers, and middleware programmatically. They offer maximum flexibility but require more boilerplate.

Express.js, Koa.js, Fastify, Hono

---

**Category 2: Explicit Module Registration (with decorator or not) **

These frameworks use TypeScript decorators or not for controllers/routes but still require explicit registration of modules and components. They use local-level HTTP frameworks like express or koa under the hood.

NestJS, LoopBack, Tsed, FeatherJS

---

Category 3: File-based Routing (Convention over Configuration)

These frameworks use file system conventions to automatically generate routes based on file structure. This is the modern meta-framework approach. All of those also use an underlying low-level HTTP framework and compile a bunch of static assets (see the documentation of Remix that is particularly transparent on that front)

Next.js (React fullstack), Remix (React fullstack), SvelteKit (Svelte fullstack), Nuxt.js (Vue fullstack), SolidStart (Solid fullstack), Analog (Angular fullstack)

---

Category 4: Convention with Auto-discovery

These frameworks use file conventions for organization but still require some explicit configuration. They auto-discover certain components.

Sails.js, AdonisJS, Meteor, Redwood.js

---

Category 5: Configuration-driven

These frameworks use configuration objects or files to define application behavior declaratively.

Hapi.js, Strapi

Decision

File-based conventions.
ChatGPT apps are by nature UI-first experiences. It's worthwhile pursuing the same conventions that drive the development of fullstack apps.

Unlike most SPA with SSR however, there isn't a single point of entry on a ChatGPT app (there is not root.tsx or app.tsx or index.ts file that should be rendered on request on /)

Downside: coding agents don't know Skybridge file-based conventions. It will be harder for them to generate code than on a explicit configuration system.