@vernikr/size-report 2.7.0 → 2.8.1

package/src/page/build.js

@@ -24,8 +24,10 @@ export function esc(s) {
  *
  * The chapters follow the page's subjects, and the order of pasting (the list below) is the order of declarations in
  * the assembled program: the calculation first, then the choice's state, the nodes, the panel, the table and the
- * assembling. The chapters are **slices of one text**: pasting glues them in a row, so the assembled page would stay
- * the same if the chapters became one file again. */
+ * assembling. A chapter that is gone leaves the page with one subject fewer rather than with a hole: the stripe over
+ * a long drawing left with the freeze it was drawn for (`src/page/app.js` says what a switch costs now). The
+ * chapters are **slices of one text**: pasting glues them in a row, so the assembled page would stay the same if
+ * the chapters became one file again. */
 export function stripModules(src) {
   return src.split('\n')
     .filter((line) => !/^import\s.*;\s*$/.test(line))
@@ -43,7 +45,7 @@ export function pageSource(file) {
 /* The list of chapters lives here rather than in the tests: one copy for the builder and for the guard
  * (`test/page-view.test.js` reads the same program and compares it with the sources). The payload chapter comes
  * first of the page's own: it is what turns the block into the data everything else reads. */
-export const PAGE_PARTS = ['./payload.js', './state.js', './dom.js', './work.js', './panel.js', './table.js', './app.js'];
+export const PAGE_PARTS = ['./payload.js', './state.js', './dom.js', './panel.js', './table.js', './app.js'];
 
 /* The form the artifact carries: the same stripping the `min` metric counts (`src/strip.js`) — comments out,
  * indentation and blank lines out — applied to what is pasted, while the sources on disk keep everything: they are
@@ -124,11 +126,13 @@ function uiText(page, loc) {
  * one (`src/page/payload.js`, `appDecode`), so the two places it is read are the encoder here and the decoder there.
  * `test/contract-data.test.js` holds the round trip between them.
  *
- * What the block leaves out besides the sparse form is the list of skipped commits: it changes with the report's own
- * commit (one with nothing to say lands in the list), and the file would stop being a **fixed point** — a rebuild
- * after its own commit would yield different bytes and the hook would commit the report forever. The page has no use
- * for the list at all: it does not show it. It stays available to the reader — `--data`, `--json` and `explain`
- * answer from the same run.
+ * What the block leaves out besides the sparse form are two facts the page does not read. The list of skipped commits
+ * changes with the report's own commit (one with nothing to say lands in the list), and the file would stop being a
+ * **fixed point** — a rebuild after its own commit would yield different bytes and the hook would commit the report
+ * forever; the page does not show it. The other is `last`, the columns the newest commit touched: the page orders the
+ * columns by the numbers themselves, which is a different fact (`src/page/table.js` says why), and the block would
+ * carry a list nothing asks for. Both stay available to the reader — `--data`, `--json` and `explain` answer from the
+ * same run.
  *
  * How much this is worth: the artifact of this repository carried 1 370 627 B of data as a snapshot per commit — 95 %
  * of the whole file — while nine tenths of the cells repeat the row above; the same history as changes is about 84 000
@@ -137,7 +141,7 @@ function uiText(page, loc) {
 /* The block's fields, in the order the encoder writes them. The shape is closed: a field added here has to be read in
  * the decoder, and the page's checks compare the block with this list rather than with a description of it. */
 export const PAGE_KEYS = ['schema', 'tool', 'report', 'hrefPrefix', 'strs', 'metrics', 'cats', 'files',
-  'catalog', 'rows', 'last', 'hist'];
+  'catalog', 'rows', 'hist'];
 
 /* The texts of the block, each written once. The dictionary is extended in the order of the walk `pagePayload` makes
  * — files in the column order, rows in the history order — and the order of the first appearance is what decides an
@@ -225,10 +229,8 @@ export function pagePayload(data) {
       r.section === null ? null : dict.of(r.section.head),
       r.section !== null && r.section.added ? 1 : 0,
       r.href === null ? null : dict.of(r.href.slice(prefix.length))]),
-    last: [],
     hist: history(keys, data.files, data.rows)
   };
-  data.last.forEach((on, i) => { if (on) out.last.push(i); });
   return out;
 }
 
@@ -255,14 +257,9 @@ export function pageHtml(data, cfg) {
     + squeezedCss(TABLE_CSS) + '\n' + squeezedCss(PAGE_CSS) + '\n</style>\n</head>\n<body>\n'
     + '<header>\n<h1>' + esc(data.report.heading) + '</h1>\n'
     + '<p class="sub">' + esc(subText(data, loc.page)) + '</p>\n</header>\n'
-    /* The stripe of the drawing stands first in the page and is fixed to the window's top edge rather than laid out
-     * with the rest: the page's shape is a grid of five rows (`src/page/app.css`), and a stripe that appeared and
-     * disappeared inside it would move the numbers under the reader's eyes every time a switch is drawn. It holds an
-     * empty child rather than a share: the length of an indeterminate stripe is the styling's business. */
-    + '<div id="bar" class="bar" role="progressbar" aria-label="' + esc(loc.page.working) + '" hidden><i></i></div>\n'
     + '<div id="panel" class="panel"></div>\n'
     + '<p id="notice" class="notice" hidden></p>\n'
-    + '<div id="shell" class="shell"><table id="grid"></table></div>\n'
+    + '<div id="shell" class="shell"><div id="grid" class="grid"></div></div>\n'
     + '<p id="state" class="state" hidden></p>\n'
     + '<p id="note" class="note"></p>\n'
     + '<script type="application/octet-stream" id="data" data-pack="base64+gzip">'

package/src/page/payload.js

@@ -15,7 +15,9 @@
  * moved (deltas against its own previous record) or disappeared, and this chapter puts the snapshots back
  * together. The whole history walk is O(number of changes) rather than O(rows × files).
  *
- * The model after `appDecode` is exactly `--data`: the calculation (`rowModel`, `totalsOf`, `cellParts`,
+ * The model after `appDecode` is exactly `--data` but for one field: the history's mark `last` (the columns the
+ * newest commit touched) is not carried, because the page orders its columns by the numbers rather than by the
+ * commit's list of paths (`src/page/table.js`). The calculation (`rowModel`, `totalsOf`, `cellParts`,
  * `valueParts`), the table and the panel know nothing about the sparse form, so there is no second way to
  * count a row. A value that did not move is **one object shared by the rows that hold it** — the heap keeps
  * the distinct numbers rather than a copy per commit — and because every consumer reads `v[metric]` and
@@ -149,8 +151,6 @@ function appRowOf(p, r, values) {
 export function appDecode(p) {
   const keys = p.metrics.map((m) => appText(p, m[0]));
   const hist = appUnroll(p, keys);
-  const last = p.files.map(() => false);
-  p.last.forEach((i) => { last[i] = true; });
   return {
     schema: p.schema,
     tool: p.tool,
@@ -162,7 +162,6 @@ export function appDecode(p) {
       paths: f[2].map((i) => p.strs[i]), category: appText(p, f[3]), categoryBy: appText(p, f[4]) })),
     catalog: p.catalog.map((e) => ({ path: appText(p, e[0]), why: appText(p, e[1]) })),
     rows: p.rows.map((r, ri) => appRowOf(p, r, hist.rows[ri])),
-    now: hist.now,
-    last: last
+    now: hist.now
   };
 }