• Renamed the npm package to @blyp/core
• Updated all documented import paths and subpath imports to @blyp/core/...
• Updated package metadata and publish configuration for scoped npm publishing
• Ensured npm publish uses public access for the scoped package
• Removed committed local temp artifacts:
  • tmp-debug/
  • .tmp-types/
• Added ignore rules to prevent those temp artifacts from being committed again
• Added agent/repo naming guidance in CLAUDE.md
• Added root README clarification that Blyphq is the GitHub org behind Blyp
• Removed accidental local-path leakage from workflow and shipped artifacts
• Fixed docs so all documented @blyp/core/... imports match actual package exports

• Zero remaining occurrences of the old package name in repo-owned files
• Zero remaining old subpath imports
• No absolute local filesystem paths remain in repo-owned files or built source maps
• bun run type-check passes
• bun run build passes
• bun run test passes (210 passing)

• npm package: @blyp/core
• version: 0.1.2

This release completes the package rename from blyp-js to @blyp/core and cleans up publish/deployment metadata.

• Fixed broken declaration shims for framework subpath imports such as blyp-js/elysia.
• Restored TypeScript visibility of createLogger from blyp-js/elysia.
• Corrected framework type shim paths to point at dist/frameworks/ instead of non-existent dist/ declaration entrypoints.

This patch release fixes TypeScript subpath declarations for framework-specific exports.

• Added regression coverage to ensure framework declaration shims keep pointing at the correct published declaration files.

If you were seeing errors like Module '"blyp-js/elysia"' has no exported member 'createLogger'.ts(2305), this release resolves that packaging issue without changing the runtime API.

• Added Better Stack connector support and logger exports.
• Added Better Stack error tracking and exception capture helpers.
• We now have a CLI:
  • GitHub: https://github.com/Blyphq/cli
  • npm: https://www.npmjs.com/package/@blyp/cli

• Compression is now 80% smaller.
• Compression is now 20x faster.

• Fixed NestJS logger state type imports used by the exception filter, interceptor, and middleware.
• Tightened HTTPCODES registry typings so built-in presets like BADREQUEST and NOT_FOUND resolve cleanly during type-checking.
• Restored clean tsc --noEmit output.

This release adds Better Stack integration, introduces the new Blyp CLI, improves compression performance, and fixes TypeScript issues in the NestJS and HTTP error code APIs.

• Version bumped to 0.1.03.

• First-party PostHog connector support across runtimes
• Dedicated connector APIs via:
  • blyp-js/posthog
  • blyp-js/sentry
  • blyp-js/otlp
• PostHog connector config via connectors.posthog
• Automatic and manual PostHog log forwarding
• PostHog error tracking via connectors.posthog.errorTracking
• Manual exception capture with createPosthogErrorTracker() and capturePosthogException()
• Sentry connector support across server, client, and Expo
• OTLP connector support across server, client, and Expo
• Expo integration support
• Request-scoped structured logging across framework integrations

• Client and Expo connector support for posthog through Blyp ingestion
• Client error and critical logs can be promoted into PostHog Error Tracking
• Improved PostHog metadata mapping for structured logs and exceptions
• Framework error logging paths now support PostHog exception capture
• Config loading now supports:
  • blyp.config.ts
  • blyp.config.mts
  • blyp.config.cts
  • blyp.config.js
  • blyp.config.mjs
  • blyp.config.cjs
  • blyp.config.json
• Queued retry delivery for client and Expo loggers
• Broader connector exports across runtimes

• PostHog exception delivery now lands correctly in Error Tracking instead of only appearing in Logs
• Exception capture and shutdown flow is more reliable for handled errors and manual captures

This release introduces first-party PostHog support for logs and error tracking on Node runtimes, expands connector support across server, client, and Expo, and adds dedicated connector APIs for PostHog, Sentry, and OTLP.

• Browser and Expo still send PostHog data through Blyp ingestion rather than directly to PostHog
• Workers remain out of scope for PostHog error tracking

• Added an Expo client.
• Added queued retry delivery for the client and Expo loggers.
• Introduced a shared remote delivery manager with retry handling, queue limits, delivery hooks, and offline/network-resume behavior.
• Exposed delivery config and remote delivery context types in the public client and Expo APIs.
• Expanded client and Expo test coverage for retries, queueing, and delivery behavior.

• Added request-scoped structured logging across the library.
• Introduced a top-level createStructuredLog(...) API with typed usage, buffered events, and explicit .emit().
• Integrated structured logging into framework request lifecycles for Elysia, Hono, Express, Fastify, NestJS, Next.js, TanStack Start, SvelteKit, and Workers.
• Suppressed default httprequest and httperror auto-logs when a structured batch is emitted.
• Added a mixed-logger guard that warns once and ignores root logger calls when a request-scoped structured logger is active.
• Updated the README and docs to document the imported createStructuredLog API and request-scoped behavior.
• Added broad framework, file logging, workers, and error-path test coverage for the new structured logging flow.

• Standalone logger support
• Client logger support with blyp-js/client
• Framework integrations for Elysia, Hono, Express, Fastify, NestJS, Next.js, TanStack Start, SvelteKit, and Workers
• Structured logging and file logging support
• TypeScript support and packaged subpath exports
• Automated npm publishing from GitHub Releases

Blyp is a high-performance logger for TypeScript applications and modern web frameworks.

```bash bun add blyp-js

@blyp/cli@0.1.53 Bug Fix: Studio crashes with Cannot find module '../dist/babel.cjs' Users running the studio via pnpm dlx @blyp/cli or any install outside the local repo would immediately hit:

Cannot find module '../dist/babel.cjs' Require stack: - .../node_modules/@blyp/cli/studio/server/assets/router-*.js

Minor change to make studio colors match main brand theme

• Replaced bundled CLI skills with live GitHub-backed installs from https://github.com/Blyphq/skills
• blyp skills install now fetches the latest main revision of the skills repo at install time
• Skill lookup now uses repo directory names such as studio-debugger

• Added clearer failure handling for missing git, GitHub/network failures, invalid remote skills, and overwrite conflicts
• Updated CLI help text and README to document the new remote install flow
• Added tests covering remote skill discovery, install resolution, and failure paths

• Removed bundled skill assets from the published CLI package
• Removed local path skill installs such as blyp skills install ./my-skill

• Studio support for Blyp projects configured with destination: "database".
• Database-backed Studio reading via direct SQL using DATABASE_URL.
• Database-aware Studio metadata, config display, and log source presentation.

• Structured/grouped traces now collapse related logs by groupId more reliably.
• Trace detail panels now show actual bundled event payloads and grouped log payloads inline.
• The first trace event opens by default in the trace timeline for faster inspection.
• Group summaries use more meaningful labels and previews instead of generic structured_log fallback text.

• Removed Prisma circular-serialization failures in Studio DB mode.
• Fixed SQL column mapping issues for Blyp database schemas using snakecase columns such as groupid, createdat, and haserror.
• Preserved grouping even when DB rows store key fields like groupId outside the JSON record payload.

This release improves Studio support for Blyp database-backed logs and makes grouped trace inspection much more usable.

• Renamed the CLI executable from blyphq to blyp
• Updated CLI help text, usage output, docs, and tests to use blyp
• Updated related Studio text to remove the old command name

• Replace any use of blyphq with blyp
• Examples:
  • blyphq studio -> blyp studio
  • blyphq health -> blyp health
  • blyphq db:init -> blyp db:init
  • blyphq --version -> blyp --version

• blyphq db:init
  • Interactive setup for Blyp database logging
  • Prompts for adapter (prisma or drizzle) and dialect (postgres or

mysql)

• Scaffolds the required blyp_logs schema
• Generates and applies migrations
• Writes blyp.config.ts automatically
• blyphq db:migrate
  • Runs the configured Prisma or Drizzle migration workflow
• blyphq db:generate
  • Runs Prisma client generation for Prisma projects

• Replaced the earlier flag-heavy database bootstrap flow with shorter

top-level commands

• Improved CLI help and README documentation for database logging setup
• Preserved idempotent schema generation to avoid duplicate models, tables, and

migration content on reruns

• Prisma + Postgres
• Prisma + MySQL
• Drizzle + Postgres
• Drizzle + MySQL

This release adds guided Blyp database logging setup to the CLI.

• Runtime table auto-creation is still not used
• Database setup remains migration-driven and explicit
• Prisma projects must expose a generated client with the blypLog delegate

for runtime logging to work

After upgrading, run:

Then use:

• Fixed bunx @blyp/cli studio failing with:

• Bundled the packaged Studio server and client assets in the published npm

• Added the runtime dependencies required for the packaged Studio SSR server

• blyphq studio now works from arbitrary projects through the published package
• The CLI still uses the repo-local Studio dev app when run inside the

blyp-cli workspace

• If a Studio server is already running locally, the CLI reuses it and opens

the requested project

This release fixes the packaged Studio experience for npm users.

Studio is not available from this installation.

package

to run outside the blyp-cli repo

Published package now includes:

• dist/
• skills/
• studio/
• Version bumped to 0.1.2

• Studio runs locally at http://localhost:3003
• Skills continue to install into .agents/skills
• This release should be used instead of 0.1.1 if you want Studio to work

from the npm package

• Fixed blyphq studio so it no longer fails with:

Workspace root could not be resolved from the current directory.

• Added a packaged Studio server so @blyp/cli can launch Studio from external projects
• Kept repo-local Studio dev behavior when running inside the blyp-cli workspace
• Added the runtime dependencies required for the packaged Studio SSR build
• Updated CLI packaging to bundle the built Studio assets for npm releases

• blyphq studio now works from arbitrary projects
• blyphq studio [targetPath] still opens the target project in Studio
• blyphq skills install behavior remains unchanged from 0.1.0

This release fixes Studio so it can be launched from any project, not just from inside the blyp-cli monorepo.

• Package version bumped to 0.1.1
• blyphq --version now reports 0.1.1
• npm publish workflow remains compatible with the existing NPM_TOKEN

GitHub secret

• Added the blyphq CLI, published as @blyp/cli
• Added blyphq studio [targetPath] to launch or reuse the local Studio app for a project
• Added blyphq health for runtime and workspace diagnostics
• Added blyphq skills install [source-or-skill-name] [--force] for skill installation

• Supports installing a local skill folder into ./.agents/skills/
• Supports installing bundled skills by name
• Supports interactive bundled-skill selection when no source is provided
• Falls back to the bundled skill picker when a local skill path is missing
• Ships with an initial bundled ai-sdk skill

• Package name: @blyp/cli
• Executable name: blyphq
• Added npm publish automation via GitHub Actions
• Configured public npm publishing with NPM_TOKEN

• Studio runs locally at http://localhost:3003
• Studio uses project-level AI configuration such as OPENROUTERAPIKEY and OPENROUTER_MODEL
• Skills are installed per project under .agents/skills