@lssm-tech/app.marketing-operationsapp.marketing-operations
Thin Marketing Operations API and durable-worker application shell.
@lssm-tech/app.marketing-operationsSource, release and verification context
Source snapshot bcc79fcc · Declared package version 0.2.0. This page combines the checked-in package guide and manifest; commands and runtime behavior were not executed in this review.
See where this package fits.
Follow a declared connection, inspect an import, then open the source guide when you need the detail.
Arrows point from a package to its direct dependency. Each count is derived from the captured manifests.
Marketing Operations application shell
This thin Bun/Node shell runs the canonical Marketing Operations API and installation workers. It requires a trusted deployment module; there is no default authentication, permitting policy, provider credential or live-spend configuration.
Set MARKETING_INSTALLATION_MODULE to a local module whose default async factory returns
createMarketingOperationsInstallation(...) from the marketing bundle. Compose its server with createMarketingOperationsServer(host) and supply readiness checks for configured persistence/authentication. Worker registrations install existing durable schedulers/queues and must drain callbacks on stop. Startup failure stops registrations already started. API readiness stays unavailable during startup/shutdown.
Run bun run start, or build and run bun run start:node. HOST defaults to loopback and PORT to 3000. Configure the public origin and an authenticated reverse proxy for external access. Requests are bounded by the installation's maximum body size; browser mutations from other origins are rejected. Health endpoints expose liveness/readiness without tenant or credential details.
Managed and self-hosted installations use the same registry and host interfaces. This is an API/worker shell: the standalone command-center frontend, managed provisioning, turnkey installation configuration and live provider qualification are still incomplete.
Declared capabilities.
This manifest does not declare a capability catalogue. Use the guide, import map and source to assess the package.
Imports and export paths.
2 entriesThese are package-manifest entry points. Named symbols listed above come from the capability catalogue; this is not an exhaustive TypeScript symbol reference.
2 imports
@lssm-tech/app.marketing-operations/mainNo export paths match this search.
Dependencies and related packages.
Runtime dependencies 3
- @hono/node-server
- catalog:
- @lssm-tech/bundle.marketing-operations
- workspace:^
- hono
- catalog:
Development dependencies 5
- @lssm-tech/lib.contracts-spec
- workspace:^
- @lssm-tech/tool.bun
- workspace:*
- @lssm-tech/tool.typescript
- workspace:*
- @types/bun
- catalog:types
- typescript
- catalog:
Package scripts.
Commands declared by this package. Review its setup requirements before running them; no command here was executed by this review.
bun src/main.tsnode dist/node/main.jscontractspec-bun-build transpile && contractspec-bun-build typescontractspec-bun-build prebuildtsgo --noEmitbun test