bc36d366bc
- Add executor configuration to Collection and Agent models in Prisma schema - Create ExecutorConfigPanel component for selecting default or custom executors - Add executor resolution logic with cascade (Agent → Collection → System Default) - Create /api/executors/verify endpoint to test custom executor connectivity - Add executor documentation page at /docs/executors with API specification - Create deployable Vercel executor template in templates/vercel-executor/ - Update MCP handlers and agent tool execution to use configurable executors - Add executor types and schemas to @tpmjs/types package Users can now deploy their own executor instances and configure collections or agents to use custom executors instead of the TPMJS default executor. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
18 lines
323 B
TypeScript
18 lines
323 B
TypeScript
import { defineConfig } from 'tsup';
|
|
|
|
export default defineConfig({
|
|
entry: [
|
|
'src/tool.ts',
|
|
'src/registry.ts',
|
|
'src/tpmjs.ts',
|
|
'src/collection.ts',
|
|
'src/agent.ts',
|
|
'src/user.ts',
|
|
'src/executor.ts',
|
|
],
|
|
format: ['esm'],
|
|
dts: true,
|
|
clean: true,
|
|
treeshake: true,
|
|
splitting: false,
|
|
});
|