Repository navigation
Refresh the dependency baseline to Effect 4.1.1 - #256
Merged
Merged
Conversation
Contributor
Type performanceMeasured with TypeScript 6.0.3 and
Marginal instantiations are measured against the matching setup without that API call:
Check times (informational)
Type instantiations are the comparison metric. Check time varies with runner load and is informational only. |
Contributor
Runtime performanceMedian of 5 independent benchmark processes on Pull request baseline
Process runtime reference points
Effect Machine change from base
Process runtime reference change from base
Regression guardNo large, noise-adjusted throughput or heap regressions detected. Versions and interpretation
Higher throughput is better; lower heap is better. Variability is the median absolute deviation across independent processes, relative to their median. Small differences on shared GitHub-hosted hardware remain informational; the required guard rejects only large changes beyond the measured noise allowance. |
Move the development baseline to Effect 4.1.1 (effect, @effect/vitest, @effect/atom-react, and the @effect/platform-* overrides) while published ranges stay ^4.0.0. Update Vite 8.3.5, Vitest 5.0.5, tstyche 7.2.5, dprint 0.64.3, @types/node 26, jsdom 30, and the React 19.3.1 development dependencies. Update devtools to chokidar 6, which requires Node.js 22.22, and build the Oxlint plugin against @oxlint/plugins and oxlint 1.90.0 while keeping its oxlint >=1.80.0 <2 peer range. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Select the polling backend through backend instead of the deprecated usePolling flag and set pollingInterval instead of the deprecated interval alias. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The classifier merged every dependency section into one map, so the unchanged effect peer range overwrote the changed development version and Effect bumps skipped the type- and runtime-performance workflows. Compare each section separately. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SandroMaglione
force-pushed
the
dependency-baseline-refresh
branch
from
November 1, 2026 09:23
02e4687 to
45c085a
Compare
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.
Summary
Refreshes the development dependency baseline. Published Effect ranges stay
^4.0.0.effect,@effect/vitest,@effect/atom-react@effect/platform-*(resolved)pnpm-workspace.yamloverrides, with all six Effect overrides at 4.1.1vitevitesttstychedprintdprint.jsonunchanged;pnpm formatproduced no changes)@types/nodejsdomreact,react-domchokidar@oxlint/pluginsdistnever imports it)oxlintNotes:
>= 22.22. The devtoolsengines.nodetherefore goes from>=22.19.0to>=22.22.0, and the README line moves with it. The watcher options now use the v6 names:backend: "polling" | "auto"replaces the deprecatedusePolling, andpollingIntervalreplaces the deprecatedinterval(second commit, with an updatedDevServerunit test).devtools:pack-checkruns the installed CLI with--watch-pollingand verifies live reload.oxlintpeer range stays>=1.80.0 <2, so consumers on oxlint 1.82 are unaffected.oxlint-plugin:pack-checkstill installs the packed plugin next tooxlint1.80.0 (the floor of the peer range), so the 1.90-built plugin is verified against the oldest supported host.vite/typescriptruntime entries are owned by Let devtools reuse compatible TypeScript and Vite installs #254, which turns them into ranges. Until then the lockfile carries both vite 8.1.5 (devtools) and 8.3.5 (root).schedulerand its peer range are owned by Remove the unused scheduler peer from the React package #253.react-dom19.3.1 brings its ownscheduler0.28, and the React package source never importsscheduler.pnpm-lock.yamlwill conflict with Remove the unused scheduler peer from the React package #253, Let devtools reuse compatible TypeScript and Vite installs #254, Check TypeScript 7 compatibility in pnpm check #255, and the oxlint port.packages/devtools/README.mdtouches the line right above Let devtools reuse compatible TypeScript and Vite installs #254's insertion. Regenerate the lockfile withpnpm installafter rebasing.scripts/ci-changes.mjsmergeddependencies,devDependencies,optionalDependencies, andpeerDependenciesinto one map with peers last. The unchangedeffect^4.0.0peer range therefore hid every Effect development bump, and the first push of this PR skipped both performance measurements. It now compares each section separately and has a regression test (third commit). Changing the classifier also triggers both workflows on this PR, so the Effect 4.1.1 bump gets measured.latest-effect: I dry-ranscripts/prepare-effect-compatibility.mjson a scratch copy of the new manifests. It resolves 4.1.1, rewrites nothing, and the manifests keep their formatting. Its unit test passes incheck:ci.Changeset
.changeset/dependency-baseline-refresh.md: patch for@typeonce/effect-machine-devtools(chokidar 6, Node.js 22.22) and@typeonce/oxlint-plugin-effect-machine(@oxlint/plugins1.90.0, unchanged peer range). The fixed group releases all four packages together.Validation
pnpm checkpassed in 2:39: 92 files / 901 tests, tstyche 41 files / 1334 assertions, consumer, all four pack checks (including the devtools CLI live reload on chokidar 6 and the Oxlint plugin diagnostic and fixer), docs, and architecture. I re-ranformat:check,docs:site:check,check:ci(31/31), anddevtools:pack-checkafter adding the engines bump and the changeset.🤖 Generated with Claude Code