@ololoepepe/controllers 0.4.0 → 0.5.0

package/CHANGELOG.md

@@ -7,6 +7,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.0] - 2026-08-29
+
+### Changed
+
+- `Json` accepts readonly arrays: the array member is now `readonly Json[]`. A
+  `ReadonlyArray` field, or anything produced by `as const`, could not be a response
+  body, because a readonly array is not assignable to a mutable one. Mutable arrays are
+  unaffected — they are assignable to readonly ones, so every body that compiled before
+  still compiles.
+
+  Breaking only for code that passes a value typed `Json` on to a JSON type declaring
+  its arrays mutable — another library's `JsonValue`, or a copy of this one. The same
+  goes for `Extract<Json, unknown[]>`, which now resolves to `never` and fails at the
+  use site rather than where it is declared.
+
 ## [0.4.0] - 2026-08-28
 
 ### Changed

package/README.md

@@ -175,12 +175,15 @@ so you only name it when you name the response as well. It is constrained to
 `Json` — what JSON can actually hold:
 
 ```ts
-export type Json = boolean | Json[] | null | number | string | {[key: string]: Json};
+export type Json = boolean | null | number | readonly Json[] | string | {[key: string]: Json};
 ```
 
 That rules out `undefined`, `bigint` (`JSON.stringify` throws on it), `symbol`
 and functions, and it checks nested fields too.
 
+Arrays are `readonly`, so a `ReadonlyArray` field or an `as const` value can be a
+body. A mutable array still passes, being assignable to a readonly one.
+
 **Describe response bodies with `type`, not `interface`.** TypeScript does not
 assign an `interface` to a type with an index signature, so an interface will not
 satisfy `Json` however JSON-shaped it is — including one nested inside a `type`:

package/dist/node/types.d.ts

@@ -20,8 +20,11 @@ export interface ControllerRequest {
  * У объектов проверяются и поля, вглубь. Цена этого в том, что TypeScript не присваивает
  * `interface` типу с индексной сигнатурой, поэтому тело ответа описывается через `type`, а не
  * через `interface`.
+ *
+ * Массив взят `readonly`, чтобы телом ответа могли стать `ReadonlyArray` и результат `as const`.
+ * Изменяемый массив подходит и так: он присваивается в `readonly`, обратное неверно.
  */
-export type Json = boolean | Json[] | null | number | string | {
+export type Json = boolean | null | number | readonly Json[] | string | {
     [key: string]: Json;
 };
 /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ololoepepe/controllers",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Common Express controllers library",
   "type": "module",
   "imports": {