Repository navigation
chore(deps): drop dependencies that only had one easy caller - #1746
Conversation
- Delete lib/effect-router: no package depends on it or imports it. Takes @tanstack/react-router with it; @effect/atom-react moves from the catalog to a direct pin in examples/effect-todo, its last user. - expect-type: import expectTypeOf from vitest, which re-exports the same package. - postgres: audit-raw-sql and restore-test run on @effect/sql-pg like the other db scripts. A failed connect still reports every restore check as failed instead of crashing. The v2 -> v3 dashboard backfill is deleted: it was a one-shot and the deployed code already decodes v3 only. - motion: the landing trace waterfall animates with the Web Animations API. - ogl: the /compare hero drops its WebGL grain canvas; each cell keeps the flat tint and halftone it already painted underneath.
Maple review🟡 Confidence 6/10 · needs attention Removes five dependencies plus the unused
What was checked
Files not reviewed (12)The review ended before it read these diffs, so nothing above vouches for them.
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 22 minutes. View limit details
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
They existed only so the web e2e suite could run a model-backed `agent.assert` that checks the alert preview chart draws both tier lines. Drop that test, the model config, and the preview job step that loaded its API key. The remaining e2e tests assert with locators and `expect`.
Maple review🟢 Confidence 10/10 · safe to merge Drops five dependencies, the unused
What was checked
|
Drops seven dependencies (and one dead workspace package) that each had a single, easily replaced caller. knip was already clean; these were all still imported somewhere.
lib/effect-router(+@tanstack/react-router)expect-type.test-d.tsfiles in query-engineexpectTypeOffromvitest(same package, re-exported)postgrespackages/dbscripts@effect/sql-pg, likemigrate.tsandcheck-row-decoding.tsmotionogl/comparehero WebGL grain canvasai,@ai-sdk/anthropicagent.assertthat the alert preview draws both tier lines)ANTHROPIC_API_KEYstep removed; the other e2e tests use locators@effect/atom-reactleaves theeffectcatalog: its last user isexamples/effect-todo, which knip ignores, so the catalog entry read as unused. The example pins it directly, aspackages/dbalready does for@effect/sql-pg.Notes
backfill-dashboard-datasource-v3.ts+ test,db:backfill:dashboards-v3). It was a one-shot from 2026-08-14, and the deployed code decodes v3 only, so it has already run. Porting 500 lines nobody will run again was not worth it.restore-test.tskeeps its failure mode: a dead connection still turns into failed checks with the report written, not a crash.fill: "both", so each cycle cancels the previous cycle's animations before re-arming.Verification
audit-raw-sql.tsagainst a freshly migrated local Postgres seeded with a raw-SQL alert rule and dashboard widget: both findings reported, jsonb read back parsed, exit 1, clean shutdown.restore-test.tsverify()(temporary harness) against the same DB: queries return counts, theto_regclassparameter and the escaped table identifier work. Against a dead port, every check fails withFailed to connectand the report still builds.astro buildpasses. In a real browser on the built site,/localwaterfall sampled over 12s runs two full cycles (bars reset to 0, grow in sequence, slowest-span pause, reset) with a flat animation count and no console errors./compare/axiomrenders both cells with tint + halftone and no canvas.e2e listselects the three alert-rule tests plus auth setup, andapps/web/e2etypechecks withaiand@ai-sdk/anthropicabsent fromnode_modules.tsrstypecheck forpackages/db,packages/query-engine,examples/effect-todo;knipclean;oxlint+oxfmt --checkon changed files;bun install --frozen-lockfileconsistent.Found while testing, not changed here:
restore-test's "migrations journal restored" check readsdrizzle.__drizzle_migrations. A database migrated with effect-orm has nodrizzleschema (it records history inpublic._effect_orm_migrations), so this check fails on any fresh database. It is worth confirming what the PlanetScale restore branch actually holds.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by CodeRabbit
Changes
Maintenance