triggeryjs
triggery
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
fix(release): pin examples to ^0.10.0 deps + refresh lockfile The Release workflow tripped on 'pnpm install --frozen-lockfile' because examples/*/package.json carried the leftover ^1.0.0 specifiers that 'pnpm changeset version' generated during the v0.10.0 cut. The lockfile still referenced ^0.9.1 from before the cut, so the resolver failed. Replaced every @triggery/* dependency in examples/* and apps/docs with ^0.10.0 to match the synchronised package version line, then refreshed pnpm-lock.yaml. Pre-commit checks all green locally: typecheck, lint, build.
main
6 hours ago
chore(deps): bump astro from 5.18.1 to 6.1.10 Bumps [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) from 5.18.1 to 6.1.10. - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/astro@6.1.10/packages/astro) --- updated-dependencies: - dependency-name: astro dependency-version: 6.1.10 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot/npm_and_yarn/astro-6.1.10
7 hours ago
Merge pull request #9 from triggeryjs/feat/v0.10 feat: v0.10 — ergonomics & bundle release
main
7 hours ago
style(core): biome format fix for coverage-v010 test file
feat/v0.10
7 hours ago
test(core): coverage backfill for v0.10 (97% funcs / 96% stmts) Coverage dropped below the 95% gate after the v0.10 refactor: - statements 94.62%, functions 90.78% - main gaps: noop inspector exports, subscribeAction guard branches, trigger.action() subscribe-on-disposed path, builder getDefaultRuntime fallback Added focused 'coverage-v010.test.ts' suite with 7 tests: - createNoopInspector full surface (record/getBuffer/getLastForTrigger/subscribe/clear) - createInspector re-export through @triggery/core/inspect - subscribeAction on nonexistent trigger -> warn + noop token - subscribeAction scope mismatch -> warn-once + noop token - trigger.action(name).subscribe on disposed trigger -> noop unsubscribe - unsubscribe idempotency - builder.handle() with no explicit runtime uses getDefaultRuntime Restores: stmts 96.41% (+1.79pp), funcs 97.16% (+6.38pp), lines 99.61% (+1.74pp)
feat/v0.10
7 hours ago
docs(v0.10): refresh benchmarks + bundle-size + /core API references 1. Fresh benchmark numbers - benchmarks/COMPARISONS.md: all 10 vs-scenarios re-measured (M1 Pro, Node 22, vitest 4.1) — updated triggery dev/prod columns + peer libraries' fresh hz numbers + 'vs Triggery' ratios recomputed - README.md: scenario table updated; in-line analysis numbers recalibrated (rxjs gap, top winners per scenario) 2. Bundle-size mentions refreshed - packages/core.mdx (en + ru): '~5 KB gzipped' → '~4.2 KB main / ~3.8 KB combined with /builder subpath (deduped)' - migration/from-v0.9.mdx (en + ru): FAQ 'Will the bundle shrink?' replaced 'stays around 5 KB' with concrete v0.9→v0.10 numbers - migration/comparison/index.mdx (en + ru): rxjs row 5 → 4.2 kB, effector row 5/6 with bindings → 4.2/5 kB - root README: bundlejs badge stays dynamic (no fixed-number drift) 3. /core API reference brought to v0.10 - create-runtime.mdx: 'inspector' option now lists InspectorFactory value; new note pointing at subscribeAction (v0.10 channel path) - types/runtime-options.mdx: same — type column + new row in semantics table for InspectorFactory - create-inspector.mdx: import block updated to /inspect subpath, explanation of createInspectorFactory factory pattern - packages/core.mdx (en + ru): mention /inspect subpath opt-in, 'last-mount-wins' → 'last-write-wins for conditions / actions'
feat/v0.10
7 hours ago
docs: deep audit fix — last-mount-wins → last-write-wins for conditions/actions across all pages Found and fixed in the systematic re-audit: V1.1 stale references (builder API was historical 'V1.1 future' — now shipped): - guide/essentials/conditions.mdx + ru/: replaced with builder subpath hint - guide/essentials/trigger-anatomy.mdx: replaced with builder subpath hint - ru/api/core/create-trigger.mdx: Aside changed from 'V1 limitation' to 'v0.10 builder API' last-mount-wins → last-write-wins for conditions/actions semantics (v0.10 dropped the stack): - guide/essentials/conditions.mdx + ru/: full section rewrite (slot, no stack pop) - guide/essentials/actions.mdx + ru/: section + recommend action-channel API - guide/essentials/runtime.mdx + ru/: lifecycle note - guide/architecture/ownership.mdx + ru/: full rewrite — slot diagram, stale-token semantics - guide/architecture/scopes.mdx + ru/: inline comment - guide/architecture/anti-spaghetti.mdx + ru/: link description - guide/ssr/strict-mode.mdx + ru/: description + stack diagram rewrite to single-slot - guide/async/debouncing-throttling.mdx + ru/: link description - guide/testing/integration-testing.mdx + ru/: StrictMode safety note - api/core/action-channel.mdx: 'top-of-stack' → 'live handler' - api/testing/mock-condition.mdx + ru/: aside rewrite - recipes/react/diagram-table-sync.mdx + ru/: useAction is additive now - examples/vite-react-diagram-table-sync/src/store.ts: motivation comment Migration guide code blocks: added missing 'import { createTrigger } from "@triggery/core/builder"' import lines (en + ru) Core source comments: 'top-of-stack handler' → 'live handler'; '(non-last-mount-wins)' → '(non-last-write-wins)' in JSDoc. Trigger-replacement last-mount-wins (semantically unchanged) intentionally left as-is in: inline-triggers.mdx, auto-discovery.mdx, vite plugin docs. hooks.ts:102 historical v0.9 reference (in semantic-change note) kept.
feat/v0.10
7 hours ago
docs: update all builder API references to use @triggery/core/builder subpath - docs/api/core/trigger-builder.mdx: import from subpath, TriggerBuilder type re-exported from main entry for ergonomic refs - docs/api/core/create-trigger.mdx: signature shows both entries; builder section header notes subpath - docs/api/core/action-channel.mdx: example uses /builder import - docs/guide/getting-started.mdx: builder example uses /builder - docs/guide/typescript/strict-mode.mdx + ru/: fix 'V1.1' stale ref → 'v0.10 builder API, import from @triggery/core/builder' - docs/guide/typescript/schema-typing.mdx + ru/: same fix - core/src/createTrigger.ts JSDoc: subpath import hint - eslint-plugin: no-non-null-assertion-in-handler + prefer-builder-trigger rule messages mention @triggery/core/builder subpath - index.ts: re-export TriggerBuilder type from main entry (type-only, zero bundle cost in prod) - benchmarks/COMPARISONS.md: verified no createTrigger refs (just numbers) - READMEs (root + per-package + templates): verified imperative form only
feat/v0.10
7 hours ago
Latest Branches
CodSpeed Performance Gauge
+30%
chore(deps): bump astro from 5.18.1 to 6.1.10
#10
7 hours ago
0b76444
dependabot/npm_and_yarn/astro-6.1.10
CodSpeed Performance Gauge
-22%
feat: v0.10 — ergonomics & bundle release
#9
7 hours ago
463adfc
feat/v0.10
CodSpeed Performance Gauge
+8%
feat(docs): /discord/ launcher + propagate community link
#8
14 hours ago
e627311
feat/docs-discord-launcher
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs