Repository navigation
chore(repo): version packages (beta) - #1017
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub. 5 Skipped Deployments
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
github-actions
Bot
force-pushed
the
changeset-release/v3
branch
3 times, most recently
from
November 14, 2026 10:10
7ddc96a to
cc7032d
Compare
HugoRCD
force-pushed
the
changeset-release/v3
branch
from
November 14, 2026 12:45
cc7032d to
9586063
Compare
Contributor
Author
|
Thank you for following the naming conventions! 🙏 |
@evlog/cli
evlog
@evlog/nuxthub
@evlog/signals
@evlog/telemetry
commit: |
Contributor
Author
Risk score: Typical (2/4)Assessed at 0a26547 from the changed files and the title, by
|
HugoRCD
force-pushed
the
changeset-release/v3
branch
from
November 16, 2026 17:53
0789787 to
9331f21
Compare
github-actions
Bot
force-pushed
the
changeset-release/v3
branch
4 times, most recently
from
November 16, 2026 21:25
75b2aea to
d3be3c0
Compare
github-actions
Bot
force-pushed
the
changeset-release/v3
branch
from
November 17, 2026 18:41
e59cc82 to
4ecd873
Compare
github-actions
Bot
force-pushed
the
changeset-release/v3
branch
from
November 17, 2026 18:46
4ecd873 to
1daf336
Compare
github-actions
Bot
force-pushed
the
changeset-release/v3
branch
from
November 17, 2026 18:50
1daf336 to
68820ed
Compare
github-actions
Bot
force-pushed
the
changeset-release/v3
branch
from
November 17, 2026 18:52
68820ed to
7c632c6
Compare
This was referenced Nov 17, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to v3, this PR will be updated.
v3is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonv3.Releases
@evlog/eve@1.0.0-beta.0
Major Changes
6e1b1acThanks @HugoRCD! - New package: evlog for eve 1.0, mounted as an eve extension withexport { default } from '@evlog/eve'inagent/extensions/evlog.ts. Each turn emits one wide event with the idsessionId:turnId, read from the session eve stores, so a turn resumed in another process is complete. Tools add fields withuseLogger()from@evlog/eve/logger, and a thrown evlog error keeps its code, status, why and fix on the event. Records are redacted in every environment, andrecord: 'minimal' | 'standard' | 'debug'with per-tool rules decides what a turn carries.evlog@3.0.0-beta.3
Major Changes
#1111
c3cf3e1Thanks @HugoRCD! - A secondlog.error()on the same request or job logger now replaces the first error instead of merging into it. Before, the event took the second error'smessageandcodebut kept fields only the first had, such as itsfixorcause, so it described neither error. Fields you set onerroryourself withlog.set(), or through theerror()context argument, are kept.To keep both failures, record the earlier one under its own key:
log.set({ receipt: { error } }).#1002
8d0cbdeThanks @HugoRCD! - On macOS and Linux, the file system drain (evlog/fs) creates its directories with mode0700and its log files with mode0600, so only the account that runs the app can read the events. Before, both followed the process umask, usually0755and0644, which let every account on the machine read them. Windows is unchanged: Node applies only the write bit there, so the files keep the permissions inherited from their folder.A directory or file that already exists keeps its mode. Run
chmod -R go= .evlogto restrict logs written before the upgrade. Another account can no longer open the new files. A log shipper running as its own user should run as the app's account, or receive the events through an HTTP drain. A container running as root that writes into a bind-mounted project on Linux now leaves files your own account cannot read: run it with--user "$(id -u):$(id -g)".#1131
8219cdfThanks @HugoRCD! - The AI block on wide events moves fromaitogen_ai, forevlog/aiandevlog/eve. Fields take the OpenTelemetry GenAI semantic convention names where the conventions define one (gen_ai.request.model,gen_ai.provider.name,gen_ai.usage.input_tokens,gen_ai.usage.cache_read.input_tokens,gen_ai.response.finish_reasons), and evlog's own fields sit under the same key in snake_case (gen_ai.calls,gen_ai.usage.cost,gen_ai.usage.estimated_cost,gen_ai.tools[].duration_ms).AILogger.getMetadata()andonUpdatereturn the same shape. eve turn events also carrygen_ai.conversation.id,gen_ai.agent.nameandgen_ai.operation.name.Migrate queries, dashboards and alerts:
ai.modelbecomesgen_ai.request.model,ai.inputTokensbecomesgen_ai.usage.input_tokens,ai.costUsdbecomesgen_ai.usage.cost,ai.estimatedCostbecomesgen_ai.usage.estimated_cost, andai.finishReasonbecomes the arraygen_ai.response.finish_reasons. The full table is on the AI SDK metadata page. The OTLP drain now sendsgen_ai.usage.cache_write.input_tokensinstead ofgen_ai.usage.cache_creation.input_tokens.#1038
fb90d8aThanks @HugoRCD! - Three optional peer ranges stop at the majors evlog is tested on:@nestjs/commonand@nestjs/corego from>=11.2.8to^11.2.8 || ^12.0.0.react-routergoes from>=7.18.5to^7.18.5 || ^8.0.0.honogoes from>=4.13.12to^4.13.12 || ^5.0.0-rc.1.evlog/honoruns on Hono 4 and on the Hono 5 release candidates. Hono 5 callsapp.onErroras middleware,(c, next)with the error onc.error, so update your own error handler when you move to it.NestJS 13, React Router 9 and Hono 6 now produce a peer warning until a release of evlog adds them.
#1134
6e1b1acThanks @HugoRCD! - Removes theevlog/eveentry point. Install@evlog/eve, replaceagent/hooks/evlog.ts(defineEvlogHook(config)) withagent/extensions/evlog.ts(export default evlog(config)from@evlog/eve), and importuseLoggerfrom@evlog/eve/logger. The migration guide lists the removed options.evlog/toolkitaddsonErrorCreated(listener), called with everyEvlogErroras it is built, andcreateMiddlewareLogger().finish()acceptsdurationMsfor an integration that knows when the work started.Minor Changes
#1036
9663cddThanks @HugoRCD! - The Better Stack adapter now sends amessage, as Better Stack's own@logtail/nodeclient does. Live tail headlines a line with it and Better Stack builds_patternfrom it, so request events now group by route. An event withoutmessagegets the headline the pretty console prints, followed by the error message, for examplePOST /api/checkout 402 in 104ms Payment failed. An event with nothing to headline gets nomessage. Amessagealready on the event, from a tagged log orlog.set({ message }), is sent unchanged.#1020
a3385c7Thanks @HugoRCD! -evlog/fastifyattaches the request logger torequest.evlog, typed asForkableLogger, sorequest.evlog.set(),.fork()and.audit()type-check. Fastify typesrequest.logas its own logger, and a module augmentation cannot change the type of an existing property:request.log.set()failed with TS2339 even though it worked at runtime, and withskipLibCheck: falsethe published declarations reported TS2717.request.logstill holds the evlog logger at runtime, so existing code keeps working. On a route thatincludeorexcludefilters out, or withenabled: false,request.evlogaccepts every call and emits nothing. On@nestjs/platform-fastify,evlog/nestjssetsrequest.evlogthe same way.#1110
e2ac261Thanks @HugoRCD! - AdderrorHandler: falseto theevlog/nuxt,evlog/nitroandevlog/nitro/v2modules. evlog's Nitro error handler is then not registered, so your own NitroerrorHandleror the framework's default answers errors. The framework default can include the error'sdata, which carrieswhy,fixandlink, for example in development, so set your ownerrorHandlerwhen they must stay private. Errors still reach the wide event. The default is unchanged.#1119
854529aThanks @HugoRCD! - Nitro v3, Nitro v2 and Nuxt: the request logger now haslog.fork(label, fn), anduseLogger()works without the event.log.fork()runs background work under a forked logger, passed tofn, that emits its own wide event withoperationand_parentRequestId. The child goes through theevlog:enrichandevlog:drainhooks like the request event, and is registered withwaitUntilwhere the runtime provides one:With Nitro's request context turned on (
experimental: { asyncContext: true }innitro.config.ts, ornitro.experimentalinnuxt.config.ts),useLogger()with no argument returns the current request logger, so services can reach it without the event. Without the flag it throws an error that names it.useLogger(event)is unchanged and works on every runtime.#1067
b8eb0deThanks @HugoRCD! - Nuxt and Nitro now run the request hooks of evlog plugins. A plugin listed inpluginsofevlog.config.tsgetsextendLoggerandonRequestStartwhen the request logger is created, andonRequestFinishafter the wide event is emitted, with the status, duration and error. Before, those apps ran only a plugin'senrich,drainandkeep, so a plugin such ascreateOtelPlugin()fromevlog/oteldid nothing there.#1099
3f0ba6bThanks @HugoRCD! - Theevlog/nuxtmodule takesclient: falsefor server-only apps:evlog: { client: false }innuxt.config.tsskips the browser plugin, the client auto-imports (log,setIdentity,clearIdentity,setMinLevel) andruntimeConfig.public.evlog. The Nitro plugin, the error handler and the server auto-imports (useLogger,log,createEvlogError) stay registered, andcreateEvlogErrorandparseErrorstay auto-imported in app code. The default,true, keeps the current behavior.#1066
cc213daThanks @HugoRCD! - Addevlog/otel.createOtelPlugin()reads the OpenTelemetry span active when a request starts and setstraceIdandspanIdon that request's wide event, so the OTLP drain links the log record to its trace.@opentelemetry/apiis a new optional peer at>=1.9.0 <2, which covers apps on OpenTelemetry JS SDK 2 and SDK 3. evlog adds no runtime dependency, and an app that does not importevlog/oteldoes not load@opentelemetry/api. The plugin runs on every integration with apluginsoption, and on Nuxt and Nitro from thepluginsofevlog.config.ts.#1044
e1e6dfeThanks @Mystery01092000! -createRequestLogger()now acceptsoperationin its options and puts it on the wide event, so a task, queue worker or cron job can name itself at creation time:createRequestLogger({ operation: 'billing:sync', requestId }). It is the same fieldlog.fork()sets on a child. Before, the option was not part ofRequestLoggerOptionsand a cast that passed it was silently dropped.#1045
2d1e756Thanks @Mystery01092000! - Addsampling.minLevel, a severity floor for wide events.initLogger({ sampling: { minLevel: 'warn' } })drops trace, debug and info wide events before sampling, from request loggers and from standalonecreateLogger()loggers such as jobs and workflows, and asampling.keeprule orkeepcallback cannot bring them back.errorandfatalevents, and audit events, always pass this floor (error events still followsampling.rates; fatal events are always kept). It works everywheresamplingis accepted:initLogger(),evlog.config.ts, the Nuxt and Nitroevlogoptions, the Vite plugin and Next.js. The top-levelminLevelis unchanged and still applies to thelogAPI only.#1112
cc25f54Thanks @HugoRCD! -evlog/workers: the loggerwithEvlogpasses to the handler now haslog.fork(label, fn). Workers has nouseLogger(), sofnreceives the forked logger as its argument. The child emits its own wide event withoperationand_parentRequestId, and the fork is registered withctx.waitUntil:The toolkit's
forkBackgroundLoggernow runs withoutstorage, for an integration withoutAsyncLocalStorage, and passes the forked logger tofnin every case.Patch Changes
#1005
b1a2570Thanks @HugoRCD! - Split adapter batches at each provider's documented per-request limits. A batch above a limit was sent as one request and rejected (usually413), and the pipeline dropped it. It is now sent as several requests that each fit:mode: 'events': request bodies under 20 MB on/batch/.Batches within the limits send the same single request as before. Retry behavior is unchanged: the drain path keeps its default retries and the pipeline path sends one attempt unless
retriesis set. A single event larger than the limit is still sent on its own, so the provider decides what to do with it.#1060
fb3df82Thanks @orshih6! -auditDiffnow reports changes toDate,Set,MapandRegExpfields as areplace(aDateis compared by timestamp, so an equal one emits nothing). Patch paths are now valid RFC 6901 JSON Pointers:~and/in keys are escaped as~0and~1, and operations on the root value use''instead of'/'.redactPathsstill matches keys that contain/or~.#1042
79882a2Thanks @onmax! - ThecreditCardbuilt-in no longer masks the digit groups of a UUID. A path such as/api/orders/00000000-0000-4000-8000-000000000000used to come out as/api/orders/****4000-****0000; it is now left as is. Card numbers written with spaces, hyphens or no separator are still masked to****1111.#1103
b5ed6cdThanks @HugoRCD! - A custom error's owntoJSONnow decides how itsdataandinternalfields are logged. A value it rewrites, such asdata: '[REDACTED]', is logged as rewritten, and a value it sets toundefinedis not logged. Before, only a key thattoJSONleft out was hidden, and a rewritten value was logged raw.EvlogErroris unchanged: logs keep itsinternal.#1019
2159dcfThanks @HugoRCD! -defineEvlogHook()fromevlog/evenow reads the v27 session events of eve 0.84 and later, eve 1.0 included. Before, it listened for the v26 names, which those versions refuse, soeve buildfailed withHook "hooks/evlog.ts" handles "message.received" was removed in session stream version 27. The hook now registers the v26 names only on eve 0.83 and earlier. A turn now ends onturn.settledand a session onsession.ended. Token usage comes fromusage.recorded, tool calls fromcall.requestedandcall.settled, approvals and sign-ins frominteraction.openedandinteraction.settled, and the user message fromdelivery.consumed. The v26 events of eve 0.72 to 0.83 keep working.eve 0.84 moved AI SDK runtime context from the
step.startedinstrumentation event to OTel integrations, sodefineEvlogInstrumentation()only applies before 0.84. On 0.84 and later, addagent/instrumentation/evlog.tsexportingotelIntegration({ runtimeContext: evlogRuntimeContext }), withotelIntegrationfromeve/instrumentation/otel.evlogRuntimeContextaccepts that input, and returns nothing for a model attempt outside a turn instead of throwing.#1101
84873d5Thanks @HugoRCD! - Theevlogexecutable runs from a directory whosepackage.jsondoes not parse. Before, it stopped withERR_INVALID_PACKAGE_CONFIGbefore reaching the CLI.#1011
6ab90fdThanks @adelrodriguez! - Typelog.fork()as always present on the request logger that an integration attaches:c.get('log')on Hono,req.logon Express and NestJS,login Elysia handlers,context.get(loggerContext)on React Router andcontext.logon oRPC. Before,forkwas optional there, soc.get('log').fork(...)failed a strict type check and neededfork!orfork?.. The newForkableLoggertype fromevlogdescribes this logger, for example in SvelteKit'sApp.Locals.useLogger()still returnsAuditableLoggerwith an optionalfork, because insidelog.fork()work it returns the forked logger, which has nofork.#1108
af7f8b4Thanks @HugoRCD! - Fix the fs drain losing events whenmaxFilesandmaxSizePerFileare both set. Once cleanup deleted the day's unsuffixed file (2026-03-14.jsonl), the next write recreated it, and because that file sorts oldest, the same cleanup deleted it straight away, so every later event that day was lost. The drain now appends to the day's newest file and rotates to the next index from there.#1117
66b1ed7Thanks @HugoRCD! - The AI section of pretty output (ai.tokens,ai.tools,ai.steps, ...) now loads on demand with the pretty-error formatter, so production bundles no longer contain it: about 3.6 kB minified and 1 kB gzipped less for an app that callsinitLogger()andlog. Pretty output is unchanged once it has loaded. An event withailogged in the same tick asinitLogger()prints as soon as it has, and if the process exits before that,aiprints as a plain field.#1116
99c6610Thanks @HugoRCD! - The pretty-error formatter (theWhy:/Fix:/ code-frame block in pretty output) now loads on demand with a dynamicimport(), so production bundles no longer contain it: about 3.7 kB minified and 600 B gzipped less for an app that callsinitLogger()andlog. Pretty output is unchanged once the formatter has loaded. An error logged in the same tick asinitLogger()prints as soon as it has, and if the process exits before that, it prints with the error message only.#1115
bfec97fThanks @HugoRCD! - Framework entries (evlog/hono,evlog/express,evlog/next,evlog/nitro,evlog/nuxt,evlog/workers, ...) andevlog/toolkitno longer load the audit helpers (withAudit,signed,auditDiff,auditOnly,auditEnricher,mockAudit). Without a bundler, each of those entries now loads about 15 kB less fromdist/(about 5 kB gzipped).log.audit()works as before, and the rootevlogentry still exports every audit helper.#1072
9aba917Thanks @HugoRCD! -createDrainPipelinefromevlog/pipeline, and theAuditActorandAuditFieldstypes fromevlog, show their documentation again in the published types and in editor hovers. Each doc block sat directly on top of another one, so TypeScript attached it to nothing.createDrainPipelinegets its description and usage example back,AuditActorthe meaning of each actor field, andAuditFieldsthe description of each reserved audit field.#1035
6a5f8abThanks @HugoRCD! - The Nitro plugin (evlog/nitroandevlog/nitro/v2, so the Nuxt module too) no longer clears a drain that another Nitro plugin set withinitLogger({ drain }). Nitro does not await plugins, so evlog's plugin finished after a synchronous plugin and reset the global drain. Request events still reachedevlog:drainhooks, but standalone loggers (createLogger, orcreateRequestLoggerin a scheduled task or queue worker) drained nowhere. The drain registered before evlog's plugin settles is now kept.#1080
beb0f47Thanks @HugoRCD! - Widen the optionalnitropeer range so thatnitro@3.0.261103-rcinstalls without a peer conflict. Before, npm failed with ERESOLVE and pnpm printed a peer warning when a project used that release candidate with the evlog 3 beta.#1109
44ed576Thanks @HugoRCD! - The Nitro v2, Nitro v3 and Nuxt integrations now use the incomingx-request-idheader as the event'srequestId, as every other integration does. Before, they ignored it and generated a UUID (or usedcf-rayon Cloudflare, which is now the fallback when nox-request-idis sent).#1098
7f6748aThanks @HugoRCD! -evlog/nitro(Nitro 3) now emits a streamed response's wide event (text/event-stream, NDJSON, chunked, AI SDK UI streams) once its body ends or the client leaves, instead of when the headers are sent. Fields set withlog.set()and errors recorded while the body streams now land on the event instead of being dropped with alog.set() called after the wide event was emittedwarning, and the event keeps the status the response was sent with. This uses h3'sonDispose, so it needs h3 2.0.1 or later; older Nitro v3 prereleases keep the header-time emit.#1011
6ab90fdThanks @adelrodriguez! -log.fork(label, fn)now runsfnon a request that evlog does not log. Before, on an Elysia route thatexcludeorincludefilters out, or withenabled: false,loghad nofork, solog.fork!(...)threwlog.fork is not a functionand the route answered 500. The work runs and emits no event. WithwaitUntil, evlog registers the work there, as it does on a logged request. If the work throws, evlog reports the error withconsole.errorandlog.fork()still resolves.#1043
c87e32fThanks @onmax! -parseError()now keeps thewhy,fixandlinkanErrorcarries as its own properties. An error class that setsfixon itself and also has adataproperty, evenundefined, used to come back withfix: undefined. Guidance found in the payload still wins.#1061
8c313b5Thanks @evlogai! - Sentry logs now carry the reserveduser.idattribute when the wide event has a user, the same attribute the official Sentry SDK sets from its user scope. The log item container also carriesversion: 2, as the Sentry logs protocol recommends. Before, the id only appeared under theuserIdkey.#1015
64bac43Thanks @HugoRCD! - On Hono, React Router and SvelteKit, a request that evlog does not log now gets a logger that accepts every call and emits nothing, onc.get('log'),context.get(loggerContext)andevent.locals.log. This covers a route thatincludeorexcludefilters out, and every route afterinitLogger({ enabled: false }). Before, nothing was attached:c.get('log').set(...)threw aTypeError, the documented HonoonErrorhandler threw as well so the request got no response, andcontext.get(loggerContext)threw in React Router loaders.log.fork()still runs its work on these requests.useLogger()still throws on them.@evlog/cli@1.0.0-beta.3
Minor Changes
#1102
9ce28dfThanks @HugoRCD! -evlog map,evlog initandevlog doctorrecognise Effect 4 apps.mapreadsHttpRouter.addandHttpRouter.routeregistrations, creditsyield* EvlogLoggerandyield* useLogger()as the request logger, and treatsrouterLayer()as the per-request event.initwritessrc/evlog.tswithinitLoggerLayerandrouterLayerbuilt fromevlog.config.ts. An app that also uses Next.js, Hono or another framework keeps that framework, and an Effect 3 app (@effect/platform) is not detected.--framework effectforces it.The "Could not detect a supported framework" error now lists every framework
mapsupports, Express and Fastify included.#1130
57e83edThanks @HugoRCD! -evlog logs --session <id>shows one AI conversation: the events whosegen_ai.conversation.idmatches, such as an eve session's turns.evlog logsalso shows an event delivered twice under the sameidempotencyKeyonce, so a retried drain write no longer appears as two events.#1075
8ee1a17Thanks @HugoRCD! -evlog mapnow records what each entry point's wide event carries. Every route inevlog.map.jsonand in--jsongains aneventkey with the dotted pathslog.set()writes (user.id,cart.items) and the literalactionof eachlog.audit()call. Comparing it between two scans shows which fields a change removes from your production logs. Routes that set nothing have noeventkey, and the existing keys are unchanged.Patch Changes
#1083
9621ea4Thanks @HugoRCD! -evlog agentsandevlog initno longer delete or duplicate text in anAGENTS.mdwhose evlog markers are not one clean pair. A file that lost<!-- evlog:end -->got a second block on one run and lost the section below it on the next. Both commands now stop withcli.AGENTS_MARKERS_UNPAIRED, exit 1 and leave the file as it is. A marker quoted in a sentence or a code fence is read as text.evlog initalso changes in four places:evlog/nitroorevlog/nitro/v3getsimport evlogalong withmodules: [evlog()]. It got the module entry with no import.errors.tsandaudit.tsparse when a service or a route starts with a digit (_3dShopErrors,_2FA_PASSWORD_CREATED) or a route holds a wildcard.npx skills addexits 1, and theAGENTS.mdblock no longer points at the skill that was not installed.evlog agentsalready did both.cli.WRITE_FAILED, which names the file and the ones written before it, under--jsontoo.evlog agentsdoes the same. Both printed a stack trace and left stdout empty.#1128
e1e33d0Thanks @HugoRCD! - Two fixes toevlog initandevlog agents.evlog init --apps apps/websets up the app. Workspace app paths were built with backslashes there, so the forward-slash form was rejected as unknown, and the JSONappvalues and the per-app headings carried backslashes. They use forward slashes on every platform, and--apps apps\webstill selects the app.npx skills addfails, the reported error is the last line it wrote before npm's update notice. Before, a failed first run could reportnpm noticeas the error.#1105
2f94179Thanks @HugoRCD! -evlog logsexits 1 on anevlog.configit cannot read, likeevlog mapandevlog config. It exited 2, the code for a misused command.evlog upgradeand--debugare marked experimental in--helpand the docs: theupgradeoutput and the debug case file may change in a 1.x release.#1101
84873d5Thanks @HugoRCD! - The CLI says what is wrong with the environment it is started in, and its output behaves in a pipe.@evlog/cli needs Node.js 22.0.0 or later, and this is Node.js 20.20.2and exit code 1. Before,evlog mapfailed there with a syntax error aboutglobSync, whiledoctor,logsand--versionstill ran on a Node the package does not support.evlog doctorno longer has a failingnodecheck or acli.NODE_TOO_OLDfinding, since it never starts there.package.jsonthat does not parse in the working directory no longer stops the launcher withERR_INVALID_PACKAGE_CONFIG.--helpprints to stdout, soevlog --help | grep mapworks. Usage shown with a usage error stays on stderr. Flags are listed the way they are typed (--min-score,-f, --follow), and positional arguments have their own section.evlog doctor 2> report.txtwrites plain text from a terminal.FORCE_COLOR=0andTERM=dumbturn colour off, and the header rule uses 24-bit colour only where the terminal supports it.evlog logs --json | head, ends the run quietly instead of with an unhandledEPIPEerror.#1059
4466f57Thanks @HugoRCD! - Every command now stops on a flag it does not declare, and on a value flag passed with no value, with exit code 2.evlog map --min-scor 90used to run with no gate and exit 0, andevlog init --dryrunwrote files. A flag written before the command name is checked too:evlog --dry-run initused to runinitfor real. A script that carries a mistyped flag today starts failing: fix the spelling.The other usage errors exit 2 as well, as the README documents: an unknown command, an invalid
--min-score,--framework,--formator--limit, andevlog map <entry>for an entry point that does not exist. An empty--min-score, which is what an unset shell variable expands to, is one of them. A bare--baselineno longer takes the flag after it as its value:evlog map --baseline --min-score 80andevlog map --baseline --cwd apps/webread both flags. Amaperror is printed as JSON under--format json, as it already was under--json.#1085
03b63a8Thanks @HugoRCD! -evlog logsreads a log of any size without its memory growing with it. Every view held each matching event until the end of the run: an 800 MB log took 1.2 GB with--limit 1. A view now keeps only the--limitevents it shows, andstatskeeps one duration per event for the percentiles. The output of every view is unchanged.#1083
9621ea4Thanks @HugoRCD! -evlog logsapplies every--wherewhen the flag is repeated. Only the last clause applied, so--where path=/a --where n=5returned events on any path. An empty--where, which is what an unset shell variable expands to, is now a usage error with exit 2.An event whose
duration,levelorserviceis not text no longer crashes every view,--jsonincluded.A
--wherevalue is a number only when it spells one exactly.zip=123no longer matches"00123", a 19-digit id no longer matches its neighbours, andamount>5000no longer matches a field that holds text such as"n/a". Write the value as the field holds it:zip=00123.#1113
6011cd1Thanks @HugoRCD! -evlog mapscores each entry point on its own handler instead of on the whole file.route.ts, server actions, TanStack Start methods), one instrumented handler used to pass every other one in the file, and each route listed the sameevent.fields. Each entry point is now read from its handler and the functions, classes and constants of the same file it names. An import such asstripemarks only the handlers that use it as sensitive.request.log.info()in a Fastify app that never registers evlog's plugin no longer passeswide-event: that is Fastify's own logger.req.logandrequest.logcount when the app registers evlog's middleware, or when the call isset,auditorfork.request.evlogis recognised.c.get('log').set()called without binding the logger first is credited in Hono.evlog map --allnames each row of a shared file by its route (index.ts · GET /health).evlog map <file>lists the other entry points of the file, andevlog map "POST /orders"inspects one by method and path.Scores drop in files where an instrumented route was covering for the others, so the rule-set version moves to 3.
--baselineagainst a map written by an earlier CLI exits 2 with the version mismatch: runevlog maponce and commit the newevlog.map.json.#1059
4466f57Thanks @HugoRCD! -evlog mapno longer scores a tree it only partly read.<file> failed to parseand counts the file as one failing entry point. With--min-score,map.minScoreor--baseline, the run stops withcli.MAP_PARSE_FAILED, exits 1, and leavesevlog.map.jsonas it was. List the file undermap.ignorewhen it is not app code.build,distandcoverageare skipped at the project root only, soserver/api/build/index.get.tsis scanned.get('/')in two routers, get distinct ids.--baselinereported regressions on an unchanged tree when they shared one. The id of every other entry point is unchanged, so a committed map stays comparable, and an entry point is still compared with itself when a second one with its method and path appears or goes. If it also moved to another file in that change, it is compared with the entry point that has its method and path and lost the most checks, then the lowest-scoring one..js,.mjsand.cjsfiles are parsed with JSX, so a Next.jspage.jsis checked instead of reported asn/a.The first and the last of these can change a verdict on code you did not touch, so the rule-set version moves to 2.
--baselineagainst a map written by an earlier CLI exits 2 with the version mismatch: runevlog maponce and commit the newevlog.map.json.#1125
4b2f220Thanks @HugoRCD! -evlog telemetry status --help(and the othertelemetrysubcommands) now shows the CLI version in the header and the fullevlog telemetry statuscommand inUSAGE, like every other command.#1059
4466f57Thanks @HugoRCD! - Newtelemetry.fail(code?)for a command that handles its own failure: it prints the error, sets an exit code and returns, so the run used to be recorded asoutcome: "success". Call it where the error is handled and the event carriesoutcome: "error"withcodeas itserrorCode.The evlog CLI calls it for every error it reports, so
evlog logswith no log directory,evlog configon an invalid file and a mistyped flag are sent as errors with theircli.*code. A failed--min-scoreor--baselinegate stays a successful run withmapGateFailed: true.#1059
4466f57Thanks @HugoRCD! - Telemetry now does what its docs say.telemetry disable, ordisableTelemetry()called inside a run, used to purge the outbox and then write its own event to it.disableTelemetry()turns off every handle created for the tool, and aflush()already sending stops at the batch in flight.EVLOG_TELEMETRY_DEBUG=1prints each run's event as the run ends and makes no request. The event is not queued either. It used to print at the next flush, and that flush sent the events.endpointhas to be the final URL.DO_NOT_TRACK=true,yesandonopt out like1, andEVLOG_TELEMETRY=false,noandofflike0.withTelemetry()records only the flags a command declares. An undeclared flag used to be sent by name, and a positional as<set>.binoption: the command people type, when it is notname. The first-run notice prints<bin> telemetry disable, so the evlog CLI's notice now saysevlog telemetry disable, notevlog-cli telemetry disable.evlog telemetry statuslists the allowlistedinit*,map*andlogs*values. The fieldsevlog logsrecords are documented.Updated dependencies [
777e3bb,4466f57,4466f57]:@evlog/telemetry@1.0.0-beta.1
Minor Changes
777e3bbThanks @HugoRCD! -run()writes every event to the on-disk outbox and POSTs only when the last successful flush is older than 15 minutes (60 minutes in CI) or 20 events have queued, capped at 50 per POST. Failed uploads stay on disk for the next command.flush()still sends immediately. Override the window withflushIntervalMsorEVLOG_TELEMETRY_FLUSH_INTERVAL_MS.createGitHubActionsTelemetry()keeps flushing after everyrun(), since runners discard the outbox when the job ends.Patch Changes
#1059
4466f57Thanks @HugoRCD! - Newtelemetry.fail(code?)for a command that handles its own failure: it prints the error, sets an exit code and returns, so the run used to be recorded asoutcome: "success". Call it where the error is handled and the event carriesoutcome: "error"withcodeas itserrorCode.The evlog CLI calls it for every error it reports, so
evlog logswith no log directory,evlog configon an invalid file and a mistyped flag are sent as errors with theircli.*code. A failed--min-scoreor--baselinegate stays a successful run withmapGateFailed: true.#1059
4466f57Thanks @HugoRCD! - Telemetry now does what its docs say.telemetry disable, ordisableTelemetry()called inside a run, used to purge the outbox and then write its own event to it.disableTelemetry()turns off every handle created for the tool, and aflush()already sending stops at the batch in flight.EVLOG_TELEMETRY_DEBUG=1prints each run's event as the run ends and makes no request. The event is not queued either. It used to print at the next flush, and that flush sent the events.endpointhas to be the final URL.DO_NOT_TRACK=true,yesandonopt out like1, andEVLOG_TELEMETRY=false,noandofflike0.withTelemetry()records only the flags a command declares. An undeclared flag used to be sent by name, and a positional as<set>.binoption: the command people type, when it is notname. The first-run notice prints<bin> telemetry disable, so the evlog CLI's notice now saysevlog telemetry disable, notevlog-cli telemetry disable.evlog telemetry statuslists the allowlistedinit*,map*andlogs*values. The fieldsevlog logsrecords are documented.