feat!: target the Elysia 2 open beta on the next release line - #371
feat!: target the Elysia 2 open beta on the next release line#371PunGrumpy wants to merge 3 commits into
Conversation
Elysia 2 "DayDream" renamed every lifecycle method and left no aliases,
so the plugin cannot support 1.4 and 2.x from one build. This branch
becomes the pre-release line published under the npm `next` dist-tag,
while 6.x stays on `latest` for Elysia 1.4.
Plugin:
- setup/request/afterHandle/error replace onStart/onRequest/onAfterHandle/onError
- .as('plugin') replaces .as('scoped')
- Logixlysia resolves to Elysia<'', 'local', LogixlysiaSingleton>; Elysia 2
inserts Scope as the second type parameter and dropped the `resolve` slot
from SingletonBase along with the resolve lifecycle
- peers move to elysia >= 2.0.0-beta.2 and typescript >= 5.7.0
Workspace:
- node adapter moves to @elysia/node with its named `node()` export
- .ws() needs the opt-in `elysia/websocket` provider before wrapWs has a route
- the example app parks its OpenAPI plugin until one ships for Elysia 2
- the evlog and bogeychan plugin benchmarks are parked for the same reason
Release:
- changesets enters pre mode with tag `next`, and pushes to a `next` branch
publish; the production docs deploy stays pinned to main
BREAKING CHANGE: requires Elysia >= 2.0.0-beta.2. Elysia 1.4 users stay on
logixlysia 6.x from the `latest` tag.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LrjUCbdtJenBTJUYo6XQo5
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
🦋 Changeset detectedLatest commit: d0461d4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThis PR adds Elysia 2 beta support. It updates Logixlysia lifecycle integration, types, WebSocket setup, package requirements, documentation, tests, benchmarks, and prerelease publishing. ChangesElysia 2 support
Estimated code review effort: 3 (Moderate) | ~25 minutes Sequence Diagram(s)sequenceDiagram
participant ElysiaApp
participant Logixlysia
participant Request
ElysiaApp->>Logixlysia: Register plugin with as('plugin')
ElysiaApp->>Logixlysia: Run setup
Request->>Logixlysia: Run request hook
Logixlysia->>Request: Initialize request context and request ID
Request->>Logixlysia: Run afterHandle or error hook
Possibly related PRs
Suggested labels: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description gives detailed technical, workspace, release, compatibility, validation, and breaking-change information. It does not include the template's explicit Related Issues or Checklist sections, but the description is otherwise complete and directly related to the changes. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
source
coderabbitai
Bot
added
enhancement
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
apps/docs/content/integrations/otel.mdx (1)
15-24: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winImport
Elysiain the OpenTelemetry example.The example uses
new Elysia()but only importslogixlysiaandinjectTraceContext, so the code sample will not run.Proposed fix
+import { Elysia } from 'elysia' import logixlysia from 'logixlysia' import { injectTraceContext } from 'logixlysia/otel'🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/docs/content/integrations/otel.mdx` around lines 15 - 24, Add the missing Elysia import to the OpenTelemetry example so the existing new Elysia() initialization is defined and runnable, without changing the plugin or request-handler logic.apps/docs/content/examples.mdx (1)
207-220: 🔒 Security & Privacy | 🟠 Major | ⚡ Quick winDo not expose
error.messagefrom the custom handler.A custom Elysia error handler controls the response message for production environments, so returning
error.messagecan expose internal error details. Return a stable public message, or map only safe, allowlisted messages.Proposed fix
- error: error.message, + error: 'Request failed',🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/docs/content/examples.mdx` around lines 207 - 220, Update the custom error handler around app.error so its response no longer returns error.message. Return a stable public-safe error message, or select only from an explicit allowlist, while preserving the existing status code and server-side pino logging.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/release.yml:
- Line 60: Update the Vercel deployment condition in the release workflow to run
for published Changesets from the next release branch as well as main, removing
the github.ref == 'refs/heads/main' restriction while preserving the published
check.
In `@apps/docs/content/faq.mdx`:
- Around line 31-38: Update the installation commands in the FAQ to include both
logixlysia@next and elysia@next, for both the bun add and npm install examples,
so fresh installs include the required Elysia 2 dependency.
---
Outside diff comments:
In `@apps/docs/content/examples.mdx`:
- Around line 207-220: Update the custom error handler around app.error so its
response no longer returns error.message. Return a stable public-safe error
message, or select only from an explicit allowlist, while preserving the
existing status code and server-side pino logging.
In `@apps/docs/content/integrations/otel.mdx`:
- Around line 15-24: Add the missing Elysia import to the OpenTelemetry example
so the existing new Elysia() initialization is defined and runnable, without
changing the plugin or request-handler logic.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: ef1231b0-534f-48d0-ade8-3dfa75742289
📒 Files selected for processing (23)
.changeset/elysia-2-open-beta.md.changeset/pre.json.github/workflows/release.ymlapps/docs/content/elysia-2.mdxapps/docs/content/examples.mdxapps/docs/content/faq.mdxapps/docs/content/integrations/otel.mdxapps/docs/content/introduction.mdxapps/docs/content/meta.tsapps/docs/content/migration-from-evlog.mdxapps/docs/content/usage.mdxapps/elysia/package.jsonapps/elysia/src/index.tsapps/elysia/src/routers/index.tsapps/elysia/src/routers/otel.tspackages/bench/index.bench.tspackages/bench/package.jsonpackages/logixlysia/README.mdpackages/logixlysia/__tests__/integration/demo-app.tspackages/logixlysia/__tests__/integration/demo-routes.test.tspackages/logixlysia/__tests__/plugin/ws-data-types.test.tspackages/logixlysia/package.jsonpackages/logixlysia/src/index.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (1)
- GitHub Check: security / 🧑⚕️ CodeQL Analysis
🧰 Additional context used
📓 Path-based instructions (6)
**/*.{ts,tsx}
📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)
**/*.{ts,tsx}: Use explicit types for function parameters and return values when they enhance clarity
Preferunknownoveranywhen the type is genuinely unknown
Use const assertions (as const) for immutable values and literal types
Leverage TypeScript's type narrowing instead of type assertionsIn TypeScript, use explicit function parameter and return types when they improve clarity; prefer
unknownoverany, useas constfor immutable literal values, and rely on type narrowing instead of assertions.
Files:
apps/docs/content/meta.tsapps/elysia/src/routers/index.tsapps/elysia/src/routers/otel.tsapps/elysia/src/index.tspackages/logixlysia/__tests__/integration/demo-app.tspackages/logixlysia/__tests__/integration/demo-routes.test.tspackages/logixlysia/__tests__/plugin/ws-data-types.test.tspackages/bench/index.bench.tspackages/logixlysia/src/index.ts
**/*.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)
**/*.{ts,tsx,js,jsx}: Use meaningful variable names instead of magic numbers - extract constants with descriptive names
Use arrow functions for callbacks and short functions
Preferfor...ofloops over.forEach()and indexedforloops
Use optional chaining (?.) and nullish coalescing (??) for safer property access
Prefer template literals over string concatenation
Use destructuring for object and array assignments
Useconstby default,letonly when reassignment is needed, nevervar
Alwaysawaitpromises in async functions - don't forget to use the return value
Useasync/awaitsyntax instead of promise chains for better readability
Handle errors appropriately in async code with try-catch blocks
Don't use async functions as Promise executors
Removeconsole.log,debugger, andalertstatements from production code
ThrowErrorobjects with descriptive messages, not strings or other values
Usetry-catchblocks meaningfully - don't catch errors just to rethrow them
Prefer early returns over nested conditionals for error cases
Keep functions focused and under reasonable cognitive complexity limits
Extract complex conditions into well-named boolean variables
Use early returns to reduce nesting
Prefer simple conditionals over nested ternary operators
Group related code together and separate concerns
Don't useeval()or assign directly todocument.cookie
Avoid spread syntax in accumulators within loops
Use top-level regex literals instead of creating them in loops
Prefer specific imports over namespace imports
Use proper image components (e.g., Next.js<Image>) over<img>tags
Files:
apps/docs/content/meta.tsapps/elysia/src/routers/index.tsapps/elysia/src/routers/otel.tsapps/elysia/src/index.tspackages/logixlysia/__tests__/integration/demo-app.tspackages/logixlysia/__tests__/integration/demo-routes.test.tspackages/logixlysia/__tests__/plugin/ws-data-types.test.tspackages/bench/index.bench.tspackages/logixlysia/src/index.ts
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
**/*.{js,jsx,ts,tsx}: Use meaningful names and extract magic numbers into descriptively named constants.
Use arrow functions for callbacks and short functions; preferfor...ofover.forEach()and indexed loops; use optional chaining, nullish coalescing, template literals, and destructuring; useconstby default,letonly when reassignment is required, and nevervar.
Await promises in async functions, prefer async/await over promise chains, handle async errors meaningfully with try-catch, and never use async functions as Promise executors.
Removeconsole.log,debugger, andalertfrom production code; throw descriptiveErrorobjects rather than strings; avoid catch-and-rethrow blocks; and prefer early returns for error cases.
Keep functions focused, limit cognitive complexity, extract complex conditions into named booleans, reduce nesting with early returns, avoid nested ternaries, and separate related concerns.
Avoid spread syntax in accumulators within loops, create reusable regular expressions outside loops, prefer specific imports over namespace imports, and avoid barrel files that re-export everything.
In Next.js, usenext/heador the App Router metadata API for head elements and use Server Components for async data fetching instead of async Client Components.
Ensure business logic, architecture, edge cases, user experience, accessibility, performance, and meaningful naming are correct; document complex logic while preferring self-documenting code.
Files:
apps/docs/content/meta.tsapps/elysia/src/routers/index.tsapps/elysia/src/routers/otel.tsapps/elysia/src/index.tspackages/logixlysia/__tests__/integration/demo-app.tspackages/logixlysia/__tests__/integration/demo-routes.test.tspackages/logixlysia/__tests__/plugin/ws-data-types.test.tspackages/bench/index.bench.tspackages/logixlysia/src/index.ts
**/index.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)
Avoid barrel files (index files that re-export everything)
Files:
apps/elysia/src/routers/index.tsapps/elysia/src/index.tspackages/logixlysia/src/index.ts
**/*.{test,spec}.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (.cursor/rules/ultracite.mdc)
**/*.{test,spec}.{ts,tsx,js,jsx}: Write assertions insideit()ortest()blocks
Avoid done callbacks in async tests - use async/await instead
Don't use.onlyor.skipin committed code
Keep test suites reasonably flat - avoid excessivedescribenesting
Files:
packages/logixlysia/__tests__/integration/demo-routes.test.tspackages/logixlysia/__tests__/plugin/ws-data-types.test.ts
**/*.{test,spec}.{js,jsx,ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
Put assertions inside
it()ortest()blocks, use async/await instead of done callbacks for async tests, never commit.onlyor.skip, and keep test suites reasonably flat.
Files:
packages/logixlysia/__tests__/integration/demo-routes.test.tspackages/logixlysia/__tests__/plugin/ws-data-types.test.ts
🔇 Additional comments (22)
packages/logixlysia/src/index.ts (2)
28-46: LGTM!Also applies to: 130-130, 141-141, 180-180, 197-197
121-129: LGTM!packages/logixlysia/package.json (1)
58-67: LGTM!Also applies to: 79-80
apps/elysia/package.json (1)
11-11: LGTM!apps/elysia/src/index.ts (1)
4-8: LGTM!apps/elysia/src/routers/index.ts (1)
2-2: LGTM!Also applies to: 42-43
apps/elysia/src/routers/otel.ts (1)
6-8: LGTM!packages/logixlysia/__tests__/integration/demo-app.ts (1)
31-33: LGTM!packages/logixlysia/__tests__/integration/demo-routes.test.ts (1)
2-2: LGTM!Also applies to: 81-83
packages/logixlysia/__tests__/plugin/ws-data-types.test.ts (1)
3-9: LGTM!Also applies to: 19-19
packages/bench/index.bench.ts (1)
1-1: LGTM!Also applies to: 162-164
packages/bench/package.json (1)
13-13: LGTM!.changeset/elysia-2-open-beta.md (1)
1-18: LGTM!.github/workflows/release.yml (1)
7-8: LGTM!apps/docs/content/elysia-2.mdx (1)
1-79: LGTM!apps/docs/content/faq.mdx (1)
40-46: LGTM!apps/docs/content/introduction.mdx (1)
33-40: LGTM!apps/docs/content/meta.ts (1)
6-6: LGTM!apps/docs/content/migration-from-evlog.mdx (1)
65-65: LGTM!apps/docs/content/usage.mdx (1)
9-13: LGTM!packages/logixlysia/README.md (1)
9-17: LGTM!.changeset/pre.json (1)
1-12: 🗄️ Data Integrity & IntegrationNo change needed for
pre.jsonbranch isolation.
origin/main:.changeset/pre.jsonis absent, and the release workflow only reads the checked-out.changeset/pre.jsonfrom the branch that runs it.
| NPM_TOKEN: "" # Workaround for https://github.com/changesets/action/pull/545 | ||
| - name: ▲ Deploy to Vercel | ||
| if: steps.changesets.outputs.published == 'true' | ||
| if: ${{ steps.changesets.outputs.published == 'true' && github.ref == 'refs/heads/main' }} |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
git fetch --no-tags origin main
git show origin/main:apps/docs/content/elysia-2.mdx >/dev/null
git show origin/main:apps/docs/content/meta.ts | rg -n "'elysia-2'"Repository: PunGrumpy/logixlysia
Length of output: 339
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== workflow release.yml excerpt =="
sed -n '45,70p' .github/workflows/release.yml 2>/dev/null || true
echo
echo "== tracked docs meta files =="
find . -path './.git' -prune -o -path './node_modules' -prune -o -type f \( -name 'meta.ts' -o -name 'meta.*' \) -print | sort
echo
echo "== elysia-2 references =="
rg -n "elysia-2|Elysia 2|next" apps docs README.md .github/workflows 2>/dev/null || trueRepository: PunGrumpy/logixlysia
Length of output: 3982
Deploy the Elysia 2 docs with next releases.
apps/docs/content/elysia-2.mdx is present locally and listed in apps/docs/content/meta.ts, but it is not in origin/main; the Vercel step only runs on main. A package published from next will expose /docs/elysia-2 on the release line while the deployed main docs page remains unavailable. Remove the main branch requirement or deploy the next docs.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/workflows/release.yml at line 60, Update the Vercel deployment
condition in the release workflow to run for published Changesets from the next
release branch as well as main, removing the github.ref == 'refs/heads/main'
restriction while preserving the published check.
| bun add logixlysia@next | ||
| ``` | ||
|
|
||
| Or with npm: | ||
|
|
||
| ```bash | ||
| npm install logixlysia | ||
| npm install logixlysia@next | ||
| ``` |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== files =="
git ls-files | sed -n '1,120p'
echo "== target file excerpt =="
if [ -f apps/docs/content/faq.mdx ]; then
nl -ba apps/docs/content/faq.mdx | sed -n '1,80p'
fi
echo "== search elysia/logixlysia references =="
rg -n "logixlysia|elysia|Elysia|logixlysia@next|elysia@next" apps/docs/package.json apps/docs/content/faq.mdx apps/docs 2>/dev/null | sed -n '1,200p'
echo "== package files =="
git ls-files | grep -E 'package\.json$' | sed -n '1,80p'
for f in $(git ls-files | grep -E 'package\.json$'); do
echo "--- $f"
sed -n '1,220p' "$f"
doneRepository: PunGrumpy/logixlysia
Length of output: 4049
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== target excerpt =="
python3 - <<'PY'
from pathlib import Path
p = Path("apps/docs/content/faq.mdx")
for i, line in enumerate(p.read_text().splitlines(), 1):
if 31 <= i <= 38:
print(f"{i:4d}: {line}")
PY
echo "== nearby Elysia 2 docs excerpt =="
python3 - <<'PY'
from pathlib import Path
p = Path("apps/docs/content/elysia-2.mdx")
lines = p.read_text().splitlines()
for i in range(1, min(len(lines), 220) + 1):
print(f"{i:4d}: {lines[i-1]}")
PY
echo "== search package references =="
python3 - <<'PY'
import re
from pathlib import Path
for p in Path(".").rglob("package.json"):
if ".git" in p.parts:
continue
try:
data = eval(p.read_text(), {"__builtins__": None})
except Exception:
continue
deps = {}
for k in ["dependencies", "devDependencies", "peerDependencies", "optionalDependencies"]:
deps.update(data.get(k, {}) or {})
hits = {k:v for k,v in deps.items() if k in {"logixlysia", "elysia"}}
if hits:
print(f"{p}: {hits}")
PY
echo "== search logixlysia/install wording =="
rg -n "logixlysia|Elysia 2|elysia@next|logixlysia@next|bun add|npm install" apps/docs/content apps/elysia apps/docs -g '*.mdx' -g '*.ts' -g '*.json' 2>/dev/null | sed -n '1,240p'Repository: PunGrumpy/logixlysia
Length of output: 22185
Install Elysia 2 with both package-manager commands.
Lines 31-37 install only logixlysia@next, but the next tag also requires Elysia >=2.0.0-beta.2. Add elysia@next to both commands so fresh installs include the required framework dependency.
Proposed fix
-bun add logixlysia@next
+bun add logixlysia@next elysia@next
...
-npm install logixlysia@next
+npm install logixlysia@next elysia@next📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| bun add logixlysia@next | |
| ``` | |
| Or with npm: | |
| ```bash | |
| npm install logixlysia | |
| npm install logixlysia@next | |
| ``` |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/docs/content/faq.mdx` around lines 31 - 38, Update the installation
commands in the FAQ to include both logixlysia@next and elysia@next, for both
the bun add and npm install examples, so fresh installs include the required
Elysia 2 dependency.
Elysia 2 "DayDream" renamed every lifecycle method with no aliases left
behind, so the plugin cannot support 1.4 and 2.x from one build. This
branch becomes the pre-release line published under the npm `next`
dist-tag, while 6.x stays on `latest` for Elysia 1.4.
Plugin:
- setup/request/afterHandle/error replace onStart/onRequest/
onAfterHandle/onError; afterHandle reads `responseValue` (the
deprecated `response` context alias was removed)
- .as('plugin') replaces .as('scoped')
- Logixlysia resolves to Elysia<'', 'local', LogixlysiaSingleton>;
Elysia 2 inserts Scope as the second type parameter and dropped the
`resolve` slot from SingletonBase along with the resolve lifecycle
- wrapWs follows the merged WS context (`ws.store`, not `ws.data.store`)
and forwards close codes/reasons
- validation errors are normalized for the TypeBox 1.x shape: the failed
property path now comes from `schemaPath`, the 1.4 `code: 'VALIDATION'`
discriminant is replaced by `status: 422` + `all`, and
`logErrorPayload` surfaces `error.value` explicitly since Elysia 2 no
longer embeds the payload in the message
- peers move to elysia >= 2.0.0-beta.11 and typescript >= 5.7.0; deps
are pinned exactly because `^2.0.0-beta.x` also matches the newer
`2.0.0-exp.x` prerelease line
Workspace:
- route hooks/schema move before the handler (Elysia 2 parameter swap)
- the node adapter moves to @elysia/node with its named `node()` export
- .ws() needs the opt-in `elysia/websocket` capability before wrapWs has
a route
- the example app's OpenAPI page returns via @elysia/openapi (Scalar),
which now ships for Elysia 2
- the evlog and bogeychan plugin-path benchmarks stay parked (both still
declare an Elysia 1 peer); their raw-logger benchmarks are unaffected
- root pins exact-mirror ^1.2.2 so the hoisted copy satisfies Elysia 2
rather than the nested Elysia 1.4.29 that evlog/bogeychan bring along
Release:
- changesets enters pre mode with tag `next`, and the release workflow
also publishes from a `next` branch; the production docs deploy stays
pinned to main
BREAKING CHANGE: requires Elysia >= 2.0.0-beta.11. Elysia 1.4 users stay
on logixlysia 6.x from the `latest` tag.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DRztm3JB5S4cCoskDPP8s9
…sia 2.0.0-beta.11 Brings the PR up to date with main and replaces the beta.2-era migration with the revalidated beta.11 one. Conflicts are resolved wholesale to the incoming branch, whose tree is the validated end state (typecheck across all packages, 375 tests, lint, and a runtime smoke test of the example app including the WebSocket echo and the restored OpenAPI page). Beyond the original beta.2 work this picks up: the route parameter swap (hooks before handler), the merged WS context (`ws.store`, not `ws.data.store`), `responseValue` in afterHandle, TypeBox 1.x validation error normalization, exact version pins (a `^2.0.0-beta.x` range also matches the newer `2.0.0-exp.x` line), the root `exact-mirror ^1.2.2` pin, and the example app's OpenAPI page via `@elysia/openapi`. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DRztm3JB5S4cCoskDPP8s9
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
github-actions
Bot
removed
the
conflict
🎬 Playground terminal recording
VHS drove
|
github-actions
Bot
added
the
conflict
2 participants
Elysia 2 "DayDream" renamed every lifecycle method and left no aliases,
so the plugin cannot support 1.4 and 2.x from one build. This branch
becomes the pre-release line published under the npm
nextdist-tag,while 6.x stays on
latestfor Elysia 1.4.Now retargeted from
2.0.0-beta.2to2.0.0-beta.11and rebased-by-mergeonto current main (sampling/enrichers, observability adapters, typed fields).
Plugin:
afterHandle reads
responseValue(the deprecatedresponsecontext alias was removed).as('plugin')replaces.as('scoped')Elysia<'', 'local', LogixlysiaSingleton>; Elysia 2inserts Scope as the second type parameter and dropped the
resolveslotfrom SingletonBase along with the resolve lifecycle
ws.store, notws.data.store) andforwards close codes/reasons
path now comes from
schemaPath, the 1.4code: 'VALIDATION'discriminant isreplaced by
status: 422+all, andlogErrorPayloadsurfaceserror.valueexplicitly since Elysia 2 no longer embeds the payload in the message
are pinned exactly because
^2.0.0-beta.xalso matches the newer2.0.0-exp.xprerelease line
Workspace:
@elysia/nodewith its namednode()export.ws()needs the opt-inelysia/websocketcapability before wrapWs has a route@elysia/openapi@next, whichnow ships for Elysia 2 (previously parked)
an Elysia 1 peer); their raw-logger benchmarks are unaffected
exact-mirror ^1.2.2so the hoisted copy satisfies Elysia 2 ratherthan the nested Elysia 1.4.29 that evlog/bogeychan bring along
Release:
next(initial version 6.8.0), and therelease workflow also publishes from a
nextbranch; the production docsdeploy stays pinned to main
Validated: typecheck across all packages, 375 tests passing, lint clean, and a
runtime smoke test of the example app on beta.11 (access logs, context tree,
WebSocket echo through wrapWs, Scalar page, RFC 9457 error responses).
BREAKING CHANGE: requires Elysia >= 2.0.0-beta.11. Elysia 1.4 users stay on
logixlysia 6.x from the
latesttag.