@niscorp/nisc 0.10.0 → 0.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,136 @@
1
1
  # @niscorp/nisc
2
2
 
3
+ ## 0.11.0
4
+
5
+ ### Minor Changes
6
+
7
+ - 87fc927: BREAKING — approved by moccadroid (owner), 2026-11-22: every @niscorp package in this release moves one minor version together; read `UPGRADING.md` and do its "Do these before you upgrade" list before moving.
8
+
9
+ `UPGRADING.md` says, package by package, what an app sees change in this release and what to do before upgrading.
10
+
11
+ ### Patch Changes
12
+
13
+ - 145b5af: Rule 16 in `AGENTS.md` names `<const>` beside `as const` as the one assertion allowed, as the shape check now reads it.
14
+ - 7842b56: `CHANGING_A_PACKAGE.md` says which packages `check:modules` covers: moss, cli and create-nisc.
15
+ `STYLE_GUIDE.md` and `REVIEW.md` are reworded in places; no rule changes.
16
+ `AGENTS.md`'s app layout says every `nisc` command reads `nisc.config.ts`, not only the ones that draw pages.
17
+ `AGENTS.md` and `CHANGING_A_PACKAGE.md` name `STYLE_GUIDE.md` as the file beside them, true in the repository and in `node_modules`. `AGENTS.md` names the write verbs (`todos.write.update`, not `todos.update`), says how Prism and a binding each index a list, names the app's own boot where it named `createAppShell(deps)`, which no package exports, and says what vex's `seedCache` does not do for a degrade app; its worked example shows a refused write.
18
+ - b18f9d3: `AGENTS.md` reads as short numbered points instead of long paragraphs, its worked example now obeys every rule it states, and the commands it names are the ones an app actually has. The part for whoever changes a package is now `CHANGING_A_PACKAGE.md`, beside it (moss's `DESIGN.md` points there).
19
+ - Updated dependencies [092b5f1]
20
+ - Updated dependencies [c9158e2]
21
+ - Updated dependencies [74a9a7a]
22
+ - Updated dependencies [16f8bf2]
23
+ - Updated dependencies [f4341b9]
24
+ - Updated dependencies [6b9b449]
25
+ - Updated dependencies [13465d1]
26
+ - Updated dependencies [7842b56]
27
+ - Updated dependencies [a8a9684]
28
+ - Updated dependencies [48138de]
29
+ - Updated dependencies [da3037e]
30
+ - Updated dependencies [e957628]
31
+ - Updated dependencies [c30562a]
32
+ - Updated dependencies [efd2368]
33
+ - Updated dependencies [ca26810]
34
+ - Updated dependencies [800a541]
35
+ - Updated dependencies [9c5367b]
36
+ - Updated dependencies [322f241]
37
+ - Updated dependencies [1135474]
38
+ - Updated dependencies [17614f1]
39
+ - Updated dependencies [16ed5d1]
40
+ - Updated dependencies [92e5048]
41
+ - Updated dependencies [5ba5973]
42
+ - Updated dependencies [4b55797]
43
+ - Updated dependencies [8d3d2c6]
44
+ - Updated dependencies [e11c912]
45
+ - Updated dependencies [7692665]
46
+ - Updated dependencies [be6cc14]
47
+ - Updated dependencies [d3fadac]
48
+ - Updated dependencies [adba9b1]
49
+ - Updated dependencies [29e51ec]
50
+ - Updated dependencies [23c4613]
51
+ - Updated dependencies [1e228d3]
52
+ - Updated dependencies [4b7d4a4]
53
+ - Updated dependencies [bf72478]
54
+ - Updated dependencies [e1db181]
55
+ - Updated dependencies [241bd4d]
56
+ - Updated dependencies [9f8e4b5]
57
+ - Updated dependencies [1b615d6]
58
+ - Updated dependencies [e7edd95]
59
+ - Updated dependencies [0a46ff6]
60
+ - Updated dependencies [59f314a]
61
+ - Updated dependencies [281108e]
62
+ - Updated dependencies [b233463]
63
+ - Updated dependencies [e2b9595]
64
+ - Updated dependencies [7aef6a7]
65
+ - Updated dependencies [79cf65c]
66
+ - Updated dependencies [e828562]
67
+ - Updated dependencies [6b01a50]
68
+ - Updated dependencies [6eef458]
69
+ - Updated dependencies [a41edf9]
70
+ - Updated dependencies [eb4ffb9]
71
+ - Updated dependencies [ae647e8]
72
+ - Updated dependencies [2effb54]
73
+ - Updated dependencies [bd996ea]
74
+ - Updated dependencies [180787b]
75
+ - Updated dependencies [d53910e]
76
+ - Updated dependencies [276f457]
77
+ - Updated dependencies [413afbd]
78
+ - Updated dependencies [1f6d37d]
79
+ - Updated dependencies [d77baf9]
80
+ - Updated dependencies [3f92c52]
81
+ - Updated dependencies [841c010]
82
+ - Updated dependencies [d93170b]
83
+ - Updated dependencies [b18f9d3]
84
+ - Updated dependencies [d85bab1]
85
+ - Updated dependencies [aeaf803]
86
+ - Updated dependencies [2b174f8]
87
+ - Updated dependencies [df79faf]
88
+ - Updated dependencies [133c0ee]
89
+ - Updated dependencies [543f79d]
90
+ - Updated dependencies [4f89d7d]
91
+ - Updated dependencies [d951434]
92
+ - Updated dependencies [b210b56]
93
+ - Updated dependencies [f61ffdd]
94
+ - Updated dependencies [88f93c0]
95
+ - Updated dependencies [c5aea8b]
96
+ - Updated dependencies [9899bd7]
97
+ - Updated dependencies [61b15e4]
98
+ - Updated dependencies [7e8f6d4]
99
+ - Updated dependencies [5c52ef5]
100
+ - Updated dependencies [66eb934]
101
+ - Updated dependencies [909ae6b]
102
+ - Updated dependencies [5eb6e6c]
103
+ - Updated dependencies [1c2b7ce]
104
+ - Updated dependencies [069efde]
105
+ - Updated dependencies [85f1536]
106
+ - Updated dependencies [d7f10ac]
107
+ - Updated dependencies [8bf0c30]
108
+ - Updated dependencies [9e5c5e3]
109
+ - Updated dependencies [8b4d6cd]
110
+ - Updated dependencies [4c6300e]
111
+ - Updated dependencies [be6e7af]
112
+ - Updated dependencies [b1e314e]
113
+ - Updated dependencies [d8dc7d9]
114
+ - Updated dependencies [b2b2d8d]
115
+ - Updated dependencies [f995714]
116
+ - Updated dependencies [df44b8e]
117
+ - Updated dependencies [a002748]
118
+ - Updated dependencies [2233113]
119
+ - Updated dependencies [04f5821]
120
+ - @niscorp/charter@0.2.0
121
+ - @niscorp/cli@0.10.0
122
+ - @niscorp/cortex@0.2.0
123
+ - @niscorp/haptic@0.3.0
124
+ - @niscorp/loom@0.6.0
125
+ - @niscorp/moss@0.10.0
126
+ - @niscorp/nova@0.6.0
127
+ - @niscorp/prism@0.4.0
128
+ - @niscorp/signal@0.2.0
129
+ - @niscorp/solid@0.2.0
130
+ - @niscorp/strata@0.2.0
131
+ - @niscorp/tide@0.2.0
132
+ - @niscorp/vex@0.5.0
133
+
3
134
  ## 0.10.0
4
135
 
5
136
  ### Minor Changes
@@ -0,0 +1,59 @@
1
+ # Changing a package
2
+
3
+ **This file is for whoever changes a `@niscorp` package.** Whoever builds an app on them reads `AGENTS.md`, beside it. Read `STYLE_GUIDE.md`, beside this file, "The packages are live", before this: what a change may do to an app that works today comes first.
4
+
5
+ ## A package follows the rules nisc sets for apps
6
+
7
+ - It runs no SQL of its own: its reads and writes are vex entries, as an app's are (`AGENTS.md`, "Using Vex").
8
+ - What crosses a boundary is parsed by a schema (`AGENTS.md` rule 13).
9
+ - `AGENTS.md` rule 16 applies in full.
10
+ - Its tables are strata sequences (`AGENTS.md` rule 17).
11
+
12
+ ## A package is made of modules
13
+
14
+ A module is a directory under `src/` with an `index.ts`.
15
+
16
+ 1. **One door.** Code outside a module imports `../<module>`, never a file inside it.
17
+ 2. **Declared dependencies.** Which module may import which is one table, in `scripts/check-modules.mts`, and the table has no cycle. A new import between two modules is a line in that table, in the same change.
18
+ 3. **One owner.** Each table and each piece of state that outlives a request belongs to one module. Nobody else writes it.
19
+ 4. **Narrow inputs.** A factory takes a typed object of the functions and values it needs. Never the whole manifest, never the whole runtime, never an object that stands in for either.
20
+ 5. **Parse where it enters.** A body, a socket message, a row, a fetched payload, a message from another process, a token: parsed by a schema in the module where it enters. No type assertion.
21
+ 6. **Nothing flat.** Only `index.ts` sits at the top of `src/`.
22
+ 7. **Limits.**
23
+ - A function of up to 200 lines is fine; 300 is the ceiling, for the rare one that reads better whole than cut up.
24
+ - A file is at most 400 lines of code, a line at most 200 wide.
25
+ - Do not split a function or a file to satisfy a number: split it when it has stopped being one thing.
26
+ - The other way round too: a file of a few lines joins the file that uses it, unless it is a published entry point.
27
+ 8. **The code speaks.** A comment is there only where the reasoning, a decision or the workings would be misread without it (`STYLE_GUIDE.md`, beside this file, "Comments"). No file headers, and no prose on the fields of a type: what an app author needs to know of an exported type is in the package's `DOCS.md`.
28
+
29
+ ## How something new gets in
30
+
31
+ In this order, and before any of it is written:
32
+
33
+ 1. Name the question it answers. It goes in the module that owns that question (a package's `DESIGN.md` says which module owns what; moss's is "How the code is laid out").
34
+ 2. If it answers none of them, it is a **feature**: a directory of its own, an entry point of its own, and it reaches the core only through a seam.
35
+ - The core never imports it, reads or writes no row of its tables, and keeps no setting of its own for it.
36
+ - The tables that are a feature's it names on itself, and its seams reach those and no other.
37
+ 3. If the seam it needs is not there, the seam is the first change, on its own, added to the module that owns the answer.
38
+ 4. A new export is a decision, not a side effect of a file needing a name: it is a line in the package's `api.txt` in the same change, and it is documented under its entry point.
39
+ 5. A statement outside vex is an entry in the ledger of `scripts/check-raw-sql.mts`, with its reason, or it does not exist. The reasons that count are a credential read before anybody is signed in, an engine's own store, and a migration.
40
+ 6. If it fits nowhere, the architecture is wrong. Say so, and propose the refactor before writing the feature. A refactor is considered every time.
41
+
42
+ A defect found on the way gets a test that fails first. A commit moves code or changes behaviour, never both.
43
+
44
+ ## The gates
45
+
46
+ All four run in `pnpm verify` and in CI.
47
+
48
+ | Run | It fails when |
49
+ |---|---|
50
+ | `pnpm check:modules` | a file other than `index.ts` sits at the top of `src/`; a module imports a file inside another module instead of its door; a module imports one the table does not give it; the table has a cycle; the core imports a feature |
51
+ | `pnpm check:api` | an entry point exports a name that is not in the package's `api.txt`, or `api.txt` names one that is no longer exported; an entry writes `export *` |
52
+ | `pnpm check:raw-sql` | a file outside the script's ledger contains a statement or a call on a database pool, or a file in the ledger contains more or fewer than its line says |
53
+ | `pnpm lint` | in moss's `src/`, or tide's Postgres store or driver (the block that lints with the compiler's types): a type assertion other than `as const`; an `any` that becomes a typed value; a written type predicate; a non-null `!`; a `function` declaration; a function over 300 lines, a file over 400 lines of code, a line over 200 wide; an inline directive that switches a rule off |
54
+
55
+ - The lint reads types, and a type from another package of the repository is read from its `dist`: `pnpm build` first, as `pnpm verify` and CI do.
56
+ - Module rules 3, 4 and 8 have no gate. They are what a review reads for.
57
+ - What two processes do to each other is in no package's tests either: those run on PGlite, which has one connection.
58
+ - `check:raw-sql` sweeps every package but vex and strata, where SQL lives.
59
+ - `check:modules` covers moss, cli and create-nisc; `check:api` covers moss. A package joins `check:modules` by being made of modules and getting an entry in `PACKAGES`; it joins `check:api` by an entry in `ENTRIES` and `pnpm check:api --write`.
package/README.md CHANGED
@@ -26,7 +26,8 @@ refuses a plan that is missing either the approval or this.
26
26
  It also carries the rules a nisc application is built by, for the versions it
27
27
  pins: [`AGENTS.md`](AGENTS.md) (the decision points, the rules, the order of
28
28
  work), [`REVIEW.md`](REVIEW.md) (what a review checks) and
29
- [`STYLE_GUIDE.md`](STYLE_GUIDE.md). They are
29
+ [`STYLE_GUIDE.md`](STYLE_GUIDE.md), with
30
+ [`CHANGING_A_PACKAGE.md`](CHANGING_A_PACKAGE.md) for whoever changes a package. They are
30
31
  written for the coding agent building the app as much as for a person. An app
31
32
  made by `npm create nisc` has a short `AGENTS.md` of its own that points here,
32
33
  so the rules it follows are always the ones for what it has installed.
package/REVIEW.md CHANGED
@@ -9,7 +9,7 @@ A review answers one question: **does the app do what it does as data, or did co
9
9
  ## How to run it
10
10
 
11
11
  1. **The gates.** The app's typecheck and its check suite (`npm run typecheck`, `npm run check`), which runs its shape check (`src/dev/shape-check.ts`) beside its own checks. An app without one is a finding: copy it from a new app (`npm create nisc`). Read what its `functions` and `allow` say, too: an allowance with a weak reason is a finding the gate cannot see. A red gate is the first finding; a boot refusal is a finding, not an environment problem. Then take the counts in "Measure first": they say where to read.
12
- 2. **Read in this order:** the charter, the entries, three actions of different kinds (a list, a form, a screen only some roles hold), the server's functions, the kit. The order follows where a fault costs most.
12
+ 2. **Read in this order:** the charter, the entries, three actions of different kinds (a list, a form, a screen only some roles are granted), the server's functions, the kit. The order follows where a fault costs most.
13
13
  3. **Go through the checklist,** then **what to look for**.
14
14
  4. **Verify before you report.** A finding is a hypothesis until the code shows it: open the file and quote the line.
15
15
  5. **Never adjust a check to make a finding go away.** A check that has to change is rewritten to protect what it protected (the rulebook's failure mode 4).
@@ -38,7 +38,7 @@ These numbers are not rules. They say where a design has drifted. In the lab app
38
38
  6. No layout or component branches on roles or capability data (rule 11) — per-principal difference is existence or a served variant.
39
39
  - **a.** Every artifact the manifest carries is pure JSON and parses its schema — a function, a `Date`, an `undefined`, or a class instance in an artifact is a code file masquerading as data. The manifest's declared code fields (`scope`, `identity`, `phrases`, `functions`, `onSession`, `runs`, `reconcilers`, a reaction's `run`, `features`, and the shell's `inputs` and `seeds` hooks) are the only exceptions; they live outside the artifact tree and are validated by running, not by this check. Moss reads the manifest by a schema when it is handed to `createServer` and refuses to boot on one that does not parse, a code field that is not a function included; this check finds it before a boot does.
40
40
  - **b.** Session code sits in the seam that describes it (rule 7a): no handler registered on `functions` that nothing calls. Tenancy resolves through `scope` and engine-side behaviors, never from a request field.
41
- - **c.** No role holding a data wildcard reaches the engine's tables, and the charter check resolves against the universe boot does (rule 10a).
41
+ - **c.** No role with a data wildcard reaches the engine's tables, and the charter check resolves against the universe boot does (rule 10a).
42
42
  - **d.** Where pages are drawn on the server: a check opens the drawn page with the real wire and target and the terminal adopts it with nothing said (rule 2a), at every window width the kit distinguishes; a page drawn for somebody goes out `private, no-store`; and every sign-in the app answers over HTTP sets the session cookie on its response and hands the page nothing (rule 12).
43
43
  7. Style guide bans (rule 16): `any`, `enum`, classes, default exports, `function` declarations, type assertions and non-null `!` — read by the compiler, not by grep, which cannot tell negation from assertion. Declared shim exceptions are honored.
44
44
  8. Decision points: each of D1–D5 is recorded in the app's `PLAN.md` with its tier — answered, delegated by name, or derived — never assumed silently.
@@ -54,7 +54,7 @@ These numbers are not rules. They say where a design has drifted. In the lab app
54
54
 
55
55
  **Formatting (rule 9).** Dates, times, counts, money and sentences built from data are Prism, in an entry's `mapping` or an endpoint's `response`. The app's "today" is in the reads' scope (the `scope` seam), never a wall-clock read.
56
56
 
57
- **Per-principal UI (rule 11).** A flag a function computes from the person's roles (`canChange`, `isStaff`) that a layout branches on is a conditional. It is existence (an action only some hold) or a served variant.
57
+ **Per-principal UI (rule 11).** A flag a function computes from the person's roles (`canChange`, `isStaff`) that a layout branches on is a conditional. It is existence (an action only some are granted) or a served variant.
58
58
 
59
59
  **`src/app` is data (checklist 6a).** Every export there is a value that serializes. A function exported from `src/app` that runs while the app runs — a layout builder called per request, a helper the server imports — is code in the artifact tree, even if everything the manifest carries passes the purity check. A builder run once as its module loads is allowed but is not row-ready: note it, as minor.
60
60
 
package/STYLE_GUIDE.md CHANGED
@@ -118,7 +118,7 @@ This binds packages only. An app's prompt may be about its app — being fitted
118
118
 
119
119
  A package's examples (`@niscorp/<package>/examples`) are its reference, as data: a document, what it is given, and what must come out. They ship with the package, and whatever shows them — nisc.dev, an agent reading `node_modules` — runs them with the version it has installed. That is what keeps a reference from falling behind the code: there is no second copy to forget.
120
120
 
121
- - **A change to what a package does changes its examples in the same commit.** A new operator, component or field gets an example. A changed result changes that example's `expected`. The package's own tests hold both — every example answers what it says, and nothing in the grammar is left without one (prism: `test/examples.test.ts`).
121
+ - **A change to what a package does changes its examples in the same commit.** A new operator, component or field gets an example. A changed result changes that example's `expected`. The package's own tests check both — every example answers what it says, and nothing in the grammar is left without one (prism: `test/examples.test.ts`).
122
122
  - **`expected` is what the engine answers, read by a person.** Record it from a run, then read it. When a test goes red because an answer moved, find out why it moved before touching `expected` — the example may be the thing that is right.
123
123
  - **An example is general**, as a prompt is ("Package prompts serve every app"): no app's names, data or domain.
124
124
  - **Examples are data.** No function, no import of the engine: `{ id, group, title, description, … }` and the documents themselves. Whoever shows one supplies the code that runs it.
@@ -166,22 +166,22 @@ Plain `name.ts` is fine when the file's role is obvious from context or when it'
166
166
 
167
167
  ## Modules
168
168
 
169
- A package that holds more than one concern is made of modules. The rules, and how something new gets in, are in AGENTS.md, "Changing a package". What is longer than a rule is here.
169
+ A package that has more than one concern is made of modules. The rules, and how something new gets in, are in `CHANGING_A_PACKAGE.md`, beside this file. What is longer than a rule is here.
170
170
 
171
171
  **A module has one door.** A module is a directory under `src/` with an `index.ts`. Code in another module imports the door (`../identity`), never a file behind it (`../identity/cache`). An entry point of the package is a door (`node/index.ts` is `@niscorp/moss/node`), or one file beside it that exports only what is published (`shells/unverified.ts` is `@niscorp/moss/unverified`). A helper is not merged into an entry file where that would export it. Which question a module answers is in the package's `DESIGN.md`, not in a comment on its door.
172
172
 
173
- **What a factory is handed is a type in its own module.** Each member is one function or one value, named for what it answers (`ShellHostConfig`, `SocketConfig`). Not the manifest, not the runtime, not an object carrying either. When the type needs a shape another module owns and may not import that module, the shape is written out where it is needed, and the wiring holds the two to each other where it hands one over. Its name ends in one of two words, by what it means and not by which module it is in. `…Config` is the argument of something another module or an app calls: what the caller chooses (`ShellHostConfig`, `DataConfig`, `IntegrationsConfig`). `…Deps` is what a module's own code hands one of its own parts: what already stands (`ServerDeps` and `RouteDeps` in the server's wiring, `OperatorDeps` in the integrations feature, `ExecuteAsDeps` inside `data`). What a thing holds while it runs is neither: it is its state (`HostState`).
173
+ **What a factory is handed is a type in its own module.** Each member is one function or one value, named for what it answers (`ShellHostConfig`, `SocketConfig`). Not the manifest, not the runtime, not an object carrying either. When the type needs a shape another module owns and may not import that module, the shape is written out where it is needed, and the wiring ties the two to each other where it hands one over. Its name ends in one of two words, by what it means and not by which module it is in. `…Config` is the argument of something another module or an app calls: what the caller chooses (`ShellHostConfig`, `DataConfig`, `IntegrationsConfig`). `…Deps` is what a module's own code hands one of its own parts: what already stands (`ServerDeps` and `RouteDeps` in the server's wiring, `OperatorDeps` in the integrations feature, `ExecuteAsDeps` inside `data`). What a thing keeps while it runs is neither: it is its state (`HostState`).
174
174
 
175
175
  **A seam belongs to the module that answers the question.** A feature reaches the core through one object it is handed when it starts. Each member is one function or one narrow value, and each is there because a feature uses it; one that stops being used is taken out, and one is not added for a feature that might want it. The object is made for the feature it is handed to. A member that reaches something owned (a table, a set of actions, the documents in a row) is bound to that feature and takes no name of one, so a feature cannot ask for what is another's; what a feature owns it says on itself, where it can be read before it runs (`Feature.tables`). No member carries a secret: a setting only one feature needs is that feature's own configuration.
176
176
 
177
- **What each gate reads.** What each fails on is the table in AGENTS.md, "Changing a package".
177
+ **What each gate reads.** What each fails on is the table in `CHANGING_A_PACKAGE.md`, "The gates".
178
178
 
179
- - `scripts/check-modules.mts`. `PACKAGES` holds, for each package it knows, which module may import which and which modules are features. It reads the relative imports and re-exports of every `.ts` and `.tsx` file under `src/`.
179
+ - `scripts/check-modules.mts`. `PACKAGES` says, for each package it knows, which module may import which and which modules are features. It reads the relative imports and re-exports of every `.ts` and `.tsx` file under `src/`.
180
180
  - `scripts/check-api.mts`. `ENTRIES` maps each entry point of a package to its source file, and the record is `packages/<name>/api.txt`, one line for each exported name. `pnpm check:api --write` records what is exported now; the diff of `api.txt` is what a reviewer reads.
181
- - `scripts/check-raw-sql.mts`. It sweeps `src/` of every package but vex and strata. Its ledger names each file that holds a statement or a call on a database pool, with its exact numbers and a reason: `credential` (it runs before a principal exists, so there is no policy to run under), `store` (an engine's own storage, in that engine's package), `tables` (a strata sequence). A number that is off fails in either direction, so a statement that is taken out comes out of the ledger in the same change.
182
- - `eslint.config.mjs`. The block for a package's modules holds rule 16 in full and the three sizes: 300 lines to a function (200 is fine; 300 is the ceiling), 400 lines of code to a file, 200 characters to a line. It lints with the compiler's types, so an `any` cannot become a typed value by being assigned, returned or handed over: `const row: Row = JSON.parse(text)` is the cast it is. Inline configuration is off, so no comment silences a rule. A package joins by having its `src/` added to the block's `files` and to the `lint` script.
181
+ - `scripts/check-raw-sql.mts`. It sweeps `src/` of every package but vex and strata. Its ledger names each file that contains a statement or a call on a database pool, with its exact numbers and a reason: `credential` (it runs before a principal exists, so there is no policy to run under), `store` (an engine's own storage, in that engine's package), `tables` (a strata sequence). A number that is off fails in either direction, so a statement that is taken out comes out of the ledger in the same change.
182
+ - `eslint.config.mjs`. The block for a package's modules has rule 16 in full and the three sizes: 300 lines to a function (200 is fine; 300 is the ceiling), 400 lines of code to a file, 200 characters to a line. It lints with the compiler's types, so an `any` cannot become a typed value by being assigned, returned or handed over: `const row: Row = JSON.parse(text)` is the cast it is. Inline configuration is off, so no comment silences a rule. A package joins by having its `src/` added to the block's `files` and to the `lint` script.
183
183
 
184
- The 200 is not the formatter's width: `.prettierrc` names 100 and nothing enforces prettier. It keeps a line from holding a paragraph; it does not make the code one width.
184
+ The 200 is not the formatter's width: `.prettierrc` names 100 and nothing enforces prettier. It keeps a line from carrying a paragraph; it does not make the code one width.
185
185
 
186
186
  ---
187
187