@nera-static/core 4.18.1 → 4.18.3

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 +13 -2
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -56,6 +56,19 @@ The package is ESM (`"type": "module"`), requires **Node 22.12 or later**, and e
56
56
 
57
57
  On Node 22 before 22.22.2, `npm install` prints `npm warn EBADENGINE` for `nopt` and `abbrev`. They come with `js-beautify` 2, which formats the HTML, and only its command-line tool uses them, never core, so the warning is harmless and every page renders the same.
58
58
 
59
+ `npm audit` reports [GHSA-3g3m-2fjr-6pw4](https://github.com/advisories/GHSA-3g3m-2fjr-6pw4) (`glob`) and [GHSA-g3hv-75wg-m249](https://github.com/advisories/GHSA-g3hv-75wg-m249) (`minimatch`) through `js-beautify` 2.0.3, and `npm audit fix` cannot resolve them: no `js-beautify` release depends on a fixed `glob` (14.0.2 or later) yet. Only its command-line tool loads `glob` and `editorconfig`; core calls `beautify.html()`, which never does, so neither advisory reaches a build. To silence the finding until core requires a fixed `js-beautify`, add this scoped override to your site's `package.json` and run `npm install`. It only replaces the copies under `js-beautify`, not the `minimatch` your other tools (eslint and the like) use, and every page renders the same. Remove it once a core release names a fixed `js-beautify` in its changelog.
60
+
61
+ ```json
62
+ "overrides": {
63
+ "js-beautify": {
64
+ "glob": "^14.0.2",
65
+ "editorconfig": {
66
+ "minimatch": "^11.0.1"
67
+ }
68
+ }
69
+ }
70
+ ```
71
+
59
72
  ```js
60
73
  import { run } from '@nera-static/core'
61
74
 
@@ -124,8 +137,6 @@ Views resolve **layered**: a site's `theme/views/<file>` overrides an installed
124
137
 
125
138
  The `NERA_THEME` environment variable overrides `theme:` in `config/app.yaml` for one run, in any of its forms (`NERA_THEME=./themes/classic nera build`), so you can build or preview another design without editing the config. An empty value falls back to `app.yaml`.
126
139
 
127
- The design lives in [`ROADMAP-themes.md`](./ROADMAP-themes.md); the consolidation that made this package importable is in [`ROADMAP-core.md`](./ROADMAP-core.md).
128
-
129
140
  ---
130
141
 
131
142
  ## 📁 Deploying to a subdirectory (`base_path`)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nera-static/core",
3
- "version": "4.18.1",
3
+ "version": "4.18.3",
4
4
  "description": "The Nera static site generator engine — the build pipeline and the layered theme/view resolver, importable by the Nera CLI, @nera-static/validate and tooling",
5
5
  "main": "./src/index.js",
6
6
  "exports": {
@@ -71,7 +71,7 @@
71
71
  "yaml": "^2.4.1"
72
72
  },
73
73
  "devDependencies": {
74
- "chokidar": "^5.0.0",
74
+ "chokidar": "^6.0.0",
75
75
  "concurrently": "^10.0.3",
76
76
  "eslint": "^10.7.0",
77
77
  "husky": "^9.1.7",