moost 0.6.6 → 0.6.8

package/README.md

@@ -1,7 +1,5 @@
 # moost
 
-**!!! This is work-in-progress library, breaking changes are expected !!!**
-
 <p align="center">
 <img src="../../moost-logo.png" width="450px"><br>
 <a  href="https://github.com/moostjs/moostjs/blob/main/LICENSE">
@@ -9,9 +7,7 @@
 </a>
 </p>
 
-Welcome to Moostjs, a metadata-driven Event Processing Framework inspired by [NestJS](https://nestjs.com/) and powered by [Wooks](https://wooks.moost.org). While Moost is currently a work-in-progress library, we're excited about its potential and invite you to explore, experiment, and contribute to its development.
-
-**Note:** As Moostjs is under active development, breaking changes can be expected.
+Welcome to Moostjs, a metadata-driven Event Processing Framework inspired by [NestJS](https://nestjs.com/) and powered by [Wooks](https://wooks.moost.org).
 
 ## Motivation
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "moost",
-  "version": "0.6.6",
+  "version": "0.6.8",
   "description": "moost",
   "keywords": [
     "composables",
@@ -21,13 +21,8 @@
     "url": "git+https://github.com/moostjs/moostjs.git",
     "directory": "packages/moost"
   },
-  "bin": {
-    "moost-skill": "./scripts/setup-skills.js"
-  },
   "files": [
-    "dist",
-    "skills",
-    "scripts/setup-skills.js"
+    "dist"
   ],
   "type": "module",
   "sideEffects": false,
@@ -46,19 +41,18 @@
     "@prostojs/infact": "^0.4.1",
     "@prostojs/logger": "^0.4.3",
     "@prostojs/mate": "^0.4.0",
-    "@wooksjs/event-core": "^0.7.8",
+    "@wooksjs/event-core": "^0.7.10",
     "hookable": "^5.5.3",
-    "wooks": "^0.7.8"
+    "wooks": "^0.7.10"
   },
   "devDependencies": {
-    "@wooksjs/event-http": "^0.7.8",
-    "@wooksjs/http-body": "^0.7.8",
+    "@wooksjs/event-http": "^0.7.10",
+    "@wooksjs/http-body": "^0.7.10",
     "vitest": "3.2.4",
-    "@moostjs/event-http": "^0.6.6"
+    "@moostjs/event-http": "^0.6.8"
   },
   "scripts": {
     "pub": "pnpm publish --access public",
-    "test": "vitest",
-    "setup-skills": "node ./scripts/setup-skills.js"
+    "test": "vitest"
   }
 }

package/scripts/setup-skills.js

@@ -1,76 +0,0 @@
-#!/usr/bin/env node
-/* prettier-ignore */
-import fs from 'fs'
-import path from 'path'
-import os from 'os'
-import { fileURLToPath } from 'url'
-
-const __dirname = path.dirname(fileURLToPath(import.meta.url))
-
-const SKILL_NAME = 'moost'
-const SKILL_SRC = path.join(__dirname, '..', 'skills', SKILL_NAME)
-
-if (!fs.existsSync(SKILL_SRC)) {
-  console.error(`No skills found at ${SKILL_SRC}`)
-  console.error('Add your SKILL.md files to the skills/' + SKILL_NAME + '/ directory first.')
-  process.exit(1)
-}
-
-const AGENTS = {
-  'Claude Code': { dir: '.claude/skills',   global: path.join(os.homedir(), '.claude', 'skills') },
-  'Cursor':      { dir: '.cursor/skills',   global: path.join(os.homedir(), '.cursor', 'skills') },
-  'Windsurf':    { dir: '.windsurf/skills', global: path.join(os.homedir(), '.windsurf', 'skills') },
-  'Codex':       { dir: '.codex/skills',    global: path.join(os.homedir(), '.codex', 'skills') },
-  'OpenCode':    { dir: '.opencode/skills', global: path.join(os.homedir(), '.opencode', 'skills') },
-}
-
-const args = process.argv.slice(2)
-const isGlobal = args.includes('--global') || args.includes('-g')
-const isPostinstall = args.includes('--postinstall')
-let installed = 0, skipped = 0
-const installedDirs = []
-
-for (const [agentName, cfg] of Object.entries(AGENTS)) {
-  const targetBase = isGlobal ? cfg.global : path.join(process.cwd(), cfg.dir)
-  const agentRootDir = path.dirname(cfg.global)
-
-  if (isPostinstall || isGlobal) {
-    if (!fs.existsSync(agentRootDir)) { skipped++; continue }
-  }
-
-  const dest = path.join(targetBase, SKILL_NAME)
-  try {
-    fs.mkdirSync(dest, { recursive: true })
-    fs.cpSync(SKILL_SRC, dest, { recursive: true })
-    console.log(`[${SKILL_NAME}] installed to ${dest}`)
-    installed++
-    if (!isGlobal) installedDirs.push(cfg.dir + '/' + SKILL_NAME)
-  } catch (err) {
-    console.warn(`[${SKILL_NAME}] failed — ${err.message}`)
-  }
-}
-
-if (!isGlobal && installedDirs.length > 0) {
-  const gitignorePath = path.join(process.cwd(), '.gitignore')
-  let gitignoreContent = ''
-  try { gitignoreContent = fs.readFileSync(gitignorePath, 'utf8') } catch {}
-  const linesToAdd = installedDirs.filter(d => !gitignoreContent.includes(d))
-  if (linesToAdd.length > 0) {
-    const hasHeader = gitignoreContent.includes('# AI agent skills')
-    const block = (gitignoreContent && !gitignoreContent.endsWith('\n') ? '\n' : '')
-      + (hasHeader ? '' : '\n# AI agent skills (auto-generated by setup-skills)\n')
-      + linesToAdd.join('\n') + '\n'
-    fs.appendFileSync(gitignorePath, block)
-    console.log(`[${SKILL_NAME}] added entries to .gitignore`)
-  }
-}
-
-if (installed === 0 && isPostinstall) {
-  // Silence is fine — no agents present, nothing to do
-} else if (installed === 0 && skipped === Object.keys(AGENTS).length) {
-  console.log('No agent directories detected. Try --global or run without it for project-local install.')
-} else if (installed === 0) {
-  console.log('Nothing installed. Run without --global to install project-locally.')
-} else {
-  console.log(`Done! Restart your AI agent to pick up the "${SKILL_NAME}" skill.`)
-}

package/skills/moost/SKILL.md

@@ -1,34 +0,0 @@
----
-name: moost
-description: Use this skill when working with moost — to create a Moost application, register controllers with @Controller(), build custom event adapters implementing TMoostAdapter, use defineMoostEventHandler() to bridge event sources, define routes with decorators, configure dependency injection with @Injectable()/@Inject()/@Provide(), create interceptors with @Intercept() and InterceptorHandler, build pipe pipelines with @Pipe()/@Resolve(), access metadata with getMoostMate(), or understand the adapter pattern used by MoostHttp, MoostWs, and MoostWf.
----
-
-# moost
-
-Moost is a metadata-driven event processing framework for TypeScript. It uses decorators and a composable architecture (powered by Wooks) to handle HTTP, CLI, WebSocket, and Workflow events — or any custom event type via the adapter pattern.
-
-## How to use this skill
-
-Read the domain file that matches the task. Do not load all files — only what you need.
-
-| Domain | File | Load when... |
-|--------|------|------------|
-| Core concepts & setup | [core.md](core.md) | Starting a new project, understanding the Moost class, registering controllers, configuring adapters |
-| Custom adapters | [custom-adapters.md](custom-adapters.md) | Building a new event adapter implementing TMoostAdapter, using defineMoostEventHandler, understanding bindHandler lifecycle |
-| Decorators & metadata | [decorators.md](decorators.md) | Creating or using decorators, reading/writing metadata with getMoostMate(), defining handler types |
-| Dependency injection | [di.md](di.md) | Configuring DI scopes, @Injectable, @Inject, @Provide, @Circular, createProvideRegistry |
-| Interceptors | [interceptors.md](interceptors.md) | Creating interceptors, understanding priority levels, @Intercept, InterceptorHandler lifecycle |
-| Pipes & resolvers | [pipes.md](pipes.md) | Building pipes, @Pipe, @Resolve, validation/transform stages, argument resolution |
-
-## Quick reference
-
-```ts
-import { Moost, Controller, Param, Intercept, Injectable, Resolve } from 'moost'
-import { defineMoostEventHandler, getMoostMate, createProvideRegistry } from 'moost'
-import type { TMoostAdapter, TMoostAdapterOptions } from 'moost'
-
-const app = new Moost()
-app.adapter(myAdapter)          // attach event adapter
-app.registerControllers(MyCtrl) // register controllers
-await app.init()                // bind all handlers, call adapter.onInit()
-```

package/skills/moost/core.md

@@ -1,174 +0,0 @@
-# Core Concepts & Setup — moost
-
-> Moost application lifecycle, controller registration, adapter attachment, and the mental model for event-driven TypeScript applications.
-
-## Concepts
-
-Moost is a **metadata-driven event processing framework**. The core mental model:
-
-1. **Controllers** — Classes decorated with `@Controller()` that contain handler methods
-2. **Adapters** — Implementations of `TMoostAdapter<H>` that bridge external event sources (HTTP, CLI, WS, etc.) to Moost's handler system
-3. **Handlers** — Methods on controllers decorated with adapter-specific decorators (e.g., `@Get()`, `@Cli()`, `@Message()`) that process events
-4. **Pipes** — Transform/resolve/validate method arguments before handler execution
-5. **Interceptors** — Cross-cutting logic (auth, logging, error handling) wrapping handler execution
-
-Unlike NestJS, Moost has **no module abstraction** — controllers are registered directly on the Moost instance.
-
-### Lifecycle
-
-```
-app.adapter(adapter)           // 1. Attach adapters
-app.registerControllers(Ctrl)  // 2. Register controller classes
-await app.init()               // 3. Bind all handlers + call adapter.onInit()
-adapter.listen(3000)           // 4. Start listening (adapter-specific)
-```
-
-During `init()`:
-1. Adapter provide registries are merged into DI
-2. All controller methods are scanned for handler metadata
-3. For each handler, `adapter.bindHandler()` is called with full context
-4. Each adapter's `onInit(moost)` hook fires last
-
-## Installation
-
-```bash
-npm install moost
-# or
-pnpm add moost
-```
-
-## API Reference
-
-### `Moost` (class)
-
-The main application class. Can be extended or used directly.
-
-```ts
-import { Moost } from 'moost'
-
-const app = new Moost()
-```
-
-#### `app.adapter<T>(a: T): T`
-
-Attaches an event adapter. Returns the adapter for chaining.
-
-```ts
-const http = app.adapter(new MoostHttp())
-http.listen(3000)
-```
-
-#### `app.registerControllers(...controllers)`
-
-Registers one or more controller classes or instances.
-
-```ts
-app.registerControllers(UserController, OrderController)
-```
-
-#### `app.init(): Promise<void>`
-
-Initializes the application: binds all controllers to all adapters, then calls each adapter's `onInit()`.
-
-#### `app.interceptor(...interceptors)`
-
-Registers global interceptors that apply to all handlers.
-
-```ts
-app.interceptor(myLoggingInterceptor)
-```
-
-#### `app.getLogger(topic?: string)`
-
-Returns a logger instance, optionally scoped to a topic.
-
-#### `app.getGlobalInterceptorHandler()`
-
-Returns an `InterceptorHandler` for global interceptors. Used by adapters for 404/not-found handlers.
-
-### `@Controller(prefix?: string)`
-
-Class decorator marking a class as a controller. The optional prefix is prepended to all handler paths.
-
-```ts
-@Controller('users')
-class UserController {
-  @Get(':id')  // resolves to /users/:id
-  getUser(@Param('id') id: string) { return { id } }
-}
-```
-
-### `@ImportController(ctrl, opts?)`
-
-Registers a nested controller within another controller, inheriting its prefix.
-
-```ts
-@Controller('api')
-@ImportController(UserController)
-@ImportController(OrderController)
-class ApiController {}
-```
-
-## Common Patterns
-
-### Pattern: Extending Moost
-
-Create an application class extending Moost. Handler methods can live directly on it.
-
-```ts
-class MyApp extends Moost {
-  @Get('health')
-  health() { return { ok: true } }
-}
-
-const app = new MyApp()
-const http = app.adapter(new MoostHttp())
-http.listen(3000)
-app.init()
-```
-
-### Pattern: Multi-adapter application
-
-Attach multiple adapters to handle different event types simultaneously.
-
-```ts
-const app = new Moost()
-const http = app.adapter(new MoostHttp())
-const ws = app.adapter(new MoostWs({ httpApp: http.getHttpApp() }))
-const cli = app.adapter(new MoostCli())
-
-app.registerControllers(HttpController, WsController, CliController)
-await app.init()
-http.listen(3000)
-```
-
-Each adapter only processes handlers matching its own type (e.g., HTTP adapter ignores `@Cli()` handlers).
-
-### Pattern: Controller-only registration
-
-Controllers are not tied to a specific adapter. The same controller class can contain handlers for multiple adapters.
-
-```ts
-@Controller('app')
-class AppController {
-  @Get('status')      // handled by HTTP adapter
-  httpStatus() { return { up: true } }
-
-  @Cli('status')      // handled by CLI adapter
-  cliStatus() { console.log('up') }
-}
-```
-
-## Best Practices
-
-- Call `app.init()` **after** registering all controllers and adapters
-- Start listening (`adapter.listen()`) before or after `init()` — the adapter buffers requests until handlers are bound
-- Use `@Controller(prefix)` to namespace related handlers
-- Keep controllers focused — one per feature area
-- Extend `Moost` for simple apps; use `registerControllers()` for larger projects
-
-## Gotchas
-
-- `app.init()` must be `await`ed — it's async because singleton controllers may need async DI resolution
-- Handler methods are bound to **all** attached adapters, but each adapter filters by handler `type` — a `@Get()` decorator is ignored by the CLI adapter
-- The order of `adapter()` calls doesn't matter for functionality but affects log output order