# Firenook 0.2.0-next.6 release notes

> Firenook 0.2.0-next.6, 18 October 2026: a stop closes the data, a killed engine is no stop, saved data opens in milliseconds, and more.

Data closed on stop, starts in milliseconds, the store's size. Published on 18 October 2026, as a preview.

`npm install --save-dev firenook@0.2.0-next.6`

[Every release](https://firenook.dev/changelog)

A newer release is out: [Firenook 0.2.0](https://firenook.dev/changelog/0.2.0), the first release for public use.

## What changed

8 changes you will notice, as the release notes give them.

1. ### A stop closes the data

   Since 0.2.0-next.3 a stop left Firestore's store file marked open (and Storage's since 0.2.0-next.4), so every start after a stop repaired it first. The console's change feed, schema index and Overview count held the store they observed, Storage held a Firestore handle, and the console's whole-database walks ignored the stop. A stop once ready, or while starting, now closes Storage, then Firestore; one that cannot close a database is reported as a failed stop.

2. ### A killed engine is no stop

   The screen said "stopped … everything is kept" whenever a stop was asked for and the engine then ended, even by a kill. Now it says the stop did not finish and that the next start checks the data first; plain mode says the same in one line.

3. ### Saved data opens in milliseconds

   The documents' count is saved with every commit instead of decoding every document at each open: a 32.6 GB store of 2.7 million documents opened in 146 s and now in 67 ms, a 4.3 GB one in 1.4 s and now in 63 ms. The first start of data an earlier release wrote counts once and saves the result.

4. ### `firenook state:inspect --state-dir DIR`

   shows what a stopped store's file holds, table by table, and how much of it is free.

5. ### `firenook state:compact --state-dir DIR`

   returns a stopped store's free pages to the disk, copying the file first (a clone where the file system has one; `--no-copy` skips it). Every document stays as it is. On the 32.6 GB store: 32.60 GB to 27.79 GB in 16 minutes.

6. ### The console Overview's Firestore card shows the store's size on disk

7. ### The old documents table is cleared

   once its documents are copied to the current layout; stores first written before 0.1.0-next.3 carried a dead copy of every document.

8. ### Published straight to `latest`

   The release workflow can now publish the CLI to `latest` in its one trusted publish, and this release used it. npm sets one tag per publish, so the CLI's `next` stays on 0.2.0-next.5 until it is moved by hand, and a preview install, which follows `next`, is not told about this release until then.

## What got faster

Measured on the same data with 0.2.0-next.5 and with 0.2.0-next.6. Lower is better.

### Opening saved data, 2.7 million documents

2,179× sooner

- [0.2.0-next.5](https://firenook.dev/changelog/0.2.0-next.5)

  146 s

- [0.2.0-next.6](https://firenook.dev/changelog/0.2.0-next.6)

  67 ms

Every multiple is rounded down. [Every release’s measures](https://firenook.dev/changelog#faster).

## Your data

What this release does to data an earlier one kept, and to the ports and protocols.

- Data saved by 0.2.0-next.6 stays readable by 0.2.0-next.5: the count is a new entry the earlier release ignores. No emulator protocol or port changed.

## How it was checked

The source it was built from, the runs it passed, and how it was published.

- Pin the engine to `767605db4248fed403523a24f6901fcc1e693d13`, the merge of [PR #93](https://github.com/firenook-dev/firenook/pull/93) on 0.2.0-next.5. Its tree is the PR head's, `7d14d9b`, which passed CI ([run 39117077846](https://github.com/firenook-dev/firenook/actions/runs/39117077846)) and the five-platform packed-install matrix ([run 39117077854](https://github.com/firenook-dev/firenook/actions/runs/39117077854)).

[The release on GitHub](https://github.com/firenook-dev/firenook/releases/tag/npm-v0.2.0-next.6).

## The latest is 0.2.0

The first release for public use. Install it, and read what changed on the way.

`npm install --save-dev firenook@0.2.0`

[Read the 0.2.0 notes](https://firenook.dev/changelog/0.2.0)
