Skip to content

docs: document the changes since 1.2.0 and add the DevTools page - #271

Draft
dangreen wants to merge 5 commits into
mainfrom
docs/changes-since-1.2.0
Draft

dangreen wants to merge 5 commits into
mainfrom
docs/changes-since-1.2.0

Conversation

@dangreen

Copy link
Copy Markdown
Member

Why

The site and the READMEs describe the 1.2.0 release, while main already carries the breaking changes of the next one: tasks on signals (#222, #223), static operators (#260), the SignalsMap classes (#261), the DevTools panel (#263) and the development builds (#236). The docs were kept on the released API on purpose; this PR brings them to what the next release ships.

What

Notes

@codecov

codecov Bot commented Sep 28, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.24%. Comparing base (cdf1238) to head (ebe2e3b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #271   +/-   ##
=======================================
  Coverage   83.24%   83.24%           
=======================================
  Files         228      228           
  Lines        4835     4835           
  Branches     1071     1071           
=======================================
  Hits         4025     4025           
  Misses        574      574           
  Partials      236      236           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

The site, the package READMEs and the DOCS.md of the agent skills now describe the code on main instead of the 1.2.0 release:

- tasks attached to the signals they fill: `task($signal, ...)` and `waitTasks($signal)` replace the tasks pool, and `hydratable()` is the whole SSR setting of a query client
- `resolved` hands falsy values through and attaches its promise as a task
- the `SignalsMap` and `IndexedSignalsMap` classes replace the map functions
- the operators return plain values for static operands, `pick` and the `text` tag are new, `concat` is gone
- `latest`, `child`, `toHtmlAttribute`, and `escapeHtml` in the SSR adapter example
- a DevTools page in the Store section with the development builds and their warnings
- the pager labels follow the pages added between the sections, and stale samples in the agera, kida and store READMEs are fixed

The benchmark and bundle size numbers come from the comparison page branch, measured on 2026-09-27.
…docs

#275 removes the warning from the development build of `@nano_kit/query`.
…deAs`, and re-measure the bundles with DI

Core Concepts gets the Aliases and Nested Contexts sections: a dependency that is not provided lives in the deepest context that provides something it reads, otherwise in the top one, and every context below shares it. The React, Preact and Svelte integration pages say how their providers nest, and the kida README gets the same two sections. The weather example with DI and the rick-and-morty SSR examples are measured again with the new DI, the other rows stay as they are.
…tivetime()` over a moment and the revalidation of a request in flight

The intl API page shows that the formatter of a `format()` message reads a signal or an accessor passed as the value and formats `null` as a missing value, and the `relativetime()` section is rewritten for a moment as the input: the unit picked by the distance between `largestUnit` and `smallestUnit`, the readings of zero, `relativeTo` and the 30-day month. Message Access in Core Concepts links the signal values, and Revalidating Cache in the query docs says that a revalidation restarts a request in flight. The skill docs are generated again.
…a revalidation in flight

The fix adds 13 B to the query client. The weather rows with Nano Kit and the rick-and-morty rows with Nano Kit, client and SSR, are measured again with the same recipe: only the chunk with the query client differs from the last measurement, by those 13 B, and the other rows stay as they are.
@dangreen
dangreen force-pushed the docs/changes-since-1.2.0 branch from 5fd5aa9 to ebe2e3b Compare October 7, 2026 16:07

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant