zerotal 1.8.1 → 1.10.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
@@ -8,6 +8,17 @@ follows the Zerotal monorepo's unified versioning.
8
8
 
9
9
  ## [Unreleased]
10
10
 
11
+ ## [1.9.0] — 2026-08-29
12
+
13
+ ### Added
14
+
15
+ - **`zerotal/shared`** — a browser-safe entry point re-exporting `@zerotal/core/shared`:
16
+ `pluralize`, `singularize`, `snakeCase`, `camelCase`, `tableNameFor`, `Str`, and the
17
+ `formatMoney` / `formatNumber` / `formatDate` formatters. Importing `zerotal` into a client
18
+ bundle drags the server in behind it; this is the subset that has no server in it, so one
19
+ definition of "how this app writes money" can be imported by both the controller and the
20
+ component instead of maintained twice.
21
+
11
22
  ## [1.4.0] — 2026-08-10
12
23
 
13
24
  ### Changed
package/README.md CHANGED
@@ -27,7 +27,7 @@ import { Auth } from "zerotal/auth";
27
27
  | `zerotal/testing` | `@zerotal/testing` |
28
28
  | `zerotal/validator` | `@zerotal/validator` |
29
29
 
30
- Core's own subpaths are mirrored 1:1, so `zerotal` is a full drop-in for `@zerotal/core`: `zerotal/logger`, `zerotal/lock`, `zerotal/storage`, `zerotal/config`, `zerotal/view`, `zerotal/helpers`, `zerotal/facades`, `zerotal/http`, `zerotal/env`, `zerotal/carbon`, `zerotal/contracts`, `zerotal/commands`, `zerotal/assets`, `zerotal/security`, `zerotal/health`, `zerotal/metrics`, `zerotal/dev`, `zerotal/build` — and `jsx-runtime`, so `"jsxImportSource": "zerotal"` works for server JSX views. The one exception is `@zerotal/core/macros/config` (a Bun macro): import it from core directly.
30
+ Core's own subpaths are mirrored 1:1, so `zerotal` is a full drop-in for `@zerotal/core`: `zerotal/logger`, `zerotal/lock`, `zerotal/storage`, `zerotal/config`, `zerotal/view`, `zerotal/helpers`, `zerotal/facades`, `zerotal/http`, `zerotal/env`, `zerotal/carbon`, `zerotal/contracts`, `zerotal/commands`, `zerotal/assets`, `zerotal/security`, `zerotal/health`, `zerotal/metrics`, `zerotal/dev`, `zerotal/build`, `zerotal/runtime` — and `jsx-runtime`, so `"jsxImportSource": "zerotal"` works for server JSX views. The one exception is `@zerotal/core/macros/config` (a Bun macro): import it from core directly.
31
31
 
32
32
  There is no behaviour here and no version skew: the meta package pins the same monorepo version as every `@zerotal/*` package it re-exports. Installing a scoped package directly is always equivalent — this package exists so a new app needs exactly one dependency to start.
33
33