Repository navigation
chore: merge main into v3 - #1120
Conversation
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Hugo Richard <hrichard206@gmail.com>
…auditDiff (#1060) Signed-off-by: Бат-Орших <34618353+orshih6@users.noreply.github.com> Co-authored-by: Hugo Richard <hrichard206@gmail.com>
Co-authored-by: Hugo Richard <hrichard206@gmail.com>
… a requester's token (#1097) Co-authored-by: evlogai[bot] <313167257+evlogai[bot]@users.noreply.github.com>
Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Hugo <HugoRCD@users.noreply.github.com>
Co-authored-by: evlogai[bot] <313167257+evlogai[bot]@users.noreply.github.com>
Co-authored-by: evlogai[bot] <313167257+evlogai[bot]@users.noreply.github.com>
Co-authored-by: evlogai[bot] <313167257+evlogai[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
Risk score: Very high (4/4)Assessed at cb0d1f2 from the changed files and the title, by
|
|
Thank you for following the naming conventions! 🙏 |
@evlog/cli
evlog
@evlog/nuxthub
@evlog/signals
@evlog/telemetry
commit: |
…-1101 # Conflicts: # packages/evlog/bench/baseline/size-budget.json
Brings the 23 commits on
mainsince #1088 intov3, including the three CLI changes the 1.0 contract needs: #1085 (logsbounded memory), #1075 (maprecords each entry point's event shape) and #1101 (the launcher refuses an unsupported Node or evlog). Like #1086 and #1088, this should land by fast-forwardingv3to this branch's head, not by a squash.Conflicts and how they were resolved
packages/evlog/src/nitro-v3/plugin.tsmain's #1098 defers the emit until a streamed body ends (h3.onDispose), andv3passes the recorded error intoemitWithTailSampling. The error is now recorded once before_evlogEmittingis set and passed to the deferredemit.packages/evlog/src/nuxt/module.tsmain'sclient: false(#1099) onv3's layout: Nitro v3 is../nitro/plugin, v2 is../nitro/v2/plugin. Theaxiom.tokendeprecation frommainis dropped, becausev3already removed the option.packages/evlog/package.jsonv3's devDependencies (NestJS 12, OTel, logtape, loglayer) plusmain's@nuxt/test-utils^4.4.0.main's other bumps merged cleanly. Peer ranges stayv3's capped ones from EVL-703.renovate.jsonv3's description, which also covers adding a new major to a peer range.apps/docs/content/3.cli/0.overview.md--debugplus #1101's--no-header.pnpm-lock.yamlmain's lockfile. Starting fromv3's lockfile instead left vite 8.3.6 and 8.3.8 side by side, which failedexamples/tanstack-starttypecheck with TS2321.Fixes the merge needed
These broke only once both branches met:
bin/evlog.mjs(fix(cli): refuse an unsupported node or evlog and behave in a pipe #1101) read the peer range as one>=x.y.z. Onv3the range is^2.31.0 || >=3.0.0-beta.0, sorange.slice(2)gave.31.0 || >=3.0.0-beta.0. The launcher then accepted any evlog from 1.0 up, and its message read "needs evlog .31.0 || >=3.0.0-beta.0 or later". It now uses the lowest floor in the range, 2.31.0, which is exact because the two alternatives meet end to end. The two "stops" tests inbin.test.tsfail withmain's launcher and pass with this one. A new test checks that 2.31.0, 2.40.1 and 3.0.0-beta.3 are all accepted.configureHandlerstays exported. refactor(next): drop unused state and one-use wrappers #1093 onmainstopped exporting it because nothing imported it there, butv3'stest/core/silent-drain-warning.test.ts(test(core): pin why _suppressDrainWarning stays #973) imports it.test/nuxt/module-type-templates.test.ts(feat(nuxt): add client: false for server-only apps #1099) expectedmain's Nitro v2 paths (../nitro/plugin,../nitro/errorHandler). They are nowv3's../nitro/v2/....The
effect-basicmap snapshot (feat(cli): detect Effect apps in map, init and doctor #1102) now carries feat(cli): record the wide event each entry point carries in evlog map #1075'seventfield:user.idandcart.itemsfor checkout,user.idfor users.Size budgets raised (
bench/baseline/size-budget.json). test(bench): add a bundle-size budget with esbuild scenarios and unpacked size #1114 set the budgets onv3alone, without the 2.x features this sync brings, and perf(core): load the pretty-error formatter on demand #1116 then lowered the gzip budgets after making the pretty-error formatter load on demand. With everything merged, Hono came out 7 B over perf(core): load the pretty-error formatter on demand #1116's budget and the unpacked tarball 2,716 B over. This PR keeps perf(core): load the pretty-error formatter on demand #1116's gzip budgets plus 100 B each, and raises the unpacked budget from 940,000 to 945,000.origin/v3was merged in again as it moved (#1109, #1114, #1112, #1115, #1119, #1116). Only #1116 conflicted, insize-budget.json, and it is resolved as above.Checks
On the merged tree:
pnpm run typecheck,pnpm run lintandpnpm run testall exit 0.@evlog/cli: 905 tests passed.evlog: 2,668 tests passed, includingtest/build/size-budget.test.ts.For the reviewer
.changeset/restore-peer-floors.md(fix(deps): restore peer dependency floors #1094) describesmain's uncapped ranges (>=11.2.8for NestJS,>=4.13.17for Hono).v3keeps its capped ones, so beta.3's changelog would print the wrong range. I left it as is, because it'smain's changeset and ships in 2.x anyway. It's one more for the EVL-604 list of 2.x changesets to delete beforechangeset pre exit, or it can be reworded here.bench/core/redact.bench.ts.pnpm installwarns about@tiptappeers inapps/docs. It comes frommain's dependency updates and doesn't affect published packages.ELI5
The 2.x branch got 23 changes since it was last copied into the 3.0 branch, and this copies them over. Where both branches changed the same lines, this keeps both changes. A few things that only broke once the two met, like the CLI's version check, are fixed here too.