@uniweb/unipress 1.0.1 → 1.1.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.
Files changed (2) hide show
  1. package/README.md +2 -2
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -90,7 +90,7 @@ Updates land via `brew upgrade unipress`. On recent Homebrew (6.x), the first `i
90
90
 
91
91
  **Manual download (Windows, or any platform without Homebrew).** Grab the asset for your platform from [the releases page](https://github.com/uniweb/unipress/releases), make it executable (Unix), and put it somewhere on your `PATH`. On macOS and Linux, `/usr/local/bin/unipress` is a common location.
92
92
 
93
- **npm.** If you already have Node ≥ 20.19:
93
+ **npm.** If you already have Node ≥ 22.12:
94
94
 
95
95
  ```bash
96
96
  npm i -g @uniweb/unipress
@@ -267,7 +267,7 @@ Applied per-field.
267
267
 
268
268
  ## Where things stand
269
269
 
270
- unipress is **pre-1.0**. The CLI is stable enough to write real documents with — the `book` template, in particular, is well-tested. Future versions may change small things, but `document.yml` files and project folders from today should keep working: scaffolded projects pin a specific foundation version, and registry artifacts are immutable.
270
+ unipress is on **1.x**, like every Uniweb package since 1.0.1. The CLI is stable enough to write real documents with — the `book` template, in particular, is well-tested. Future versions may change small things, and a change you may need to act on arrives as a minor version, but `document.yml` files and project folders from today should keep working: scaffolded projects pin a specific foundation version, and registry artifacts are immutable.
271
271
 
272
272
  **Foundations are fetched on first use.** The bundled templates pin foundations served from `https://uniweb.github.io/unipress/foundations/…`; the first compile downloads and caches the one your `document.yml` names (alongside the Typst binary). To iterate on a foundation locally, pass `--foundation <path>` pointing at a built foundation directory; to point at a different registry, set `UNIWEB_REGISTRY_URL`.
273
273
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@uniweb/unipress",
3
- "version": "1.0.1",
3
+ "version": "1.1.0",
4
4
  "description": "Compile a content directory into a document (PDF, EPUB, Paged.js HTML, Typst source bundle, DOCX, XLSX) using a Uniweb foundation. Five built-in templates: book, monograph, report, data-report, directory.",
5
5
  "type": "module",
6
6
  "publishConfig": {
@@ -41,7 +41,7 @@
41
41
  "url": "https://github.com/uniweb/unipress/issues"
42
42
  },
43
43
  "engines": {
44
- "node": ">=20.19"
44
+ "node": ">=22.12"
45
45
  },
46
46
  "dependencies": {
47
47
  "handlebars": "^4.7.8",
@@ -49,11 +49,11 @@
49
49
  "prompts": "^2.4.2",
50
50
  "react": "^19.0.0",
51
51
  "react-dom": "^19.0.0",
52
- "@uniweb/build": "~1.0.1",
53
- "@uniweb/runtime": "~1.0.1",
54
- "@uniweb/core": "~1.0.1",
55
- "@uniweb/content-reader": "~1.2.8",
56
- "@uniweb/semantic-parser": "~1.5.1"
52
+ "@uniweb/build": "~1.1.0",
53
+ "@uniweb/core": "~1.1.0",
54
+ "@uniweb/semantic-parser": "~1.5.1",
55
+ "@uniweb/runtime": "~1.1.0",
56
+ "@uniweb/content-reader": "~1.2.8"
57
57
  },
58
58
  "devDependencies": {
59
59
  "vitest": "^4.1.7"