@nifrajs/content 5.12.1 → 5.13.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 (3) hide show
  1. package/CHANGELOG.md +6 -0
  2. package/package.json +1 -1
  3. package/src/fs.ts +3 -2
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # @nifrajs/content
2
2
 
3
+ ## 5.13.0
4
+
5
+ ### Patch Changes
6
+
7
+ - efc9ce4: Correct the filesystem collection comment so it names `bakeCollection` and `fromBaked` as the edge snapshot.
8
+
3
9
  ## 5.12.1
4
10
 
5
11
  No changes in this release.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nifrajs/content",
3
- "version": "5.12.1",
3
+ "version": "5.13.0",
4
4
  "description": "Typed, schema-validated content collections for nifra - Markdown + frontmatter, framework-agnostic.",
5
5
  "keywords": [
6
6
  "bun",
package/src/fs.ts CHANGED
@@ -1,7 +1,8 @@
1
1
  /**
2
2
  * Filesystem-backed content collections - `defineCollection` reads a directory of Markdown files and
3
- * gives you a typed, validated API over them. Build/server-time (Bun/Node/Deno); for the edge, bake the
4
- * entries at build (the manifest approach `@nifrajs/web/fs` uses for routes) - tracked as a follow-up.
3
+ * gives you a typed, validated API over them. Build/server-time (Bun/Node/Deno). An edge bundle reads
4
+ * a snapshot instead: `bakeCollection` where the filesystem is available, `fromBaked` on the edge.
5
+ * Both are in `@nifrajs/content`.
5
6
  */
6
7
  import type { BigIntStats } from "node:fs"
7
8
  import { readdir, readFile, stat as statPath } from "node:fs/promises"