@niscorp/moss 0.8.0 → 0.8.1

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 +8 -0
  2. package/DOCS.md +8 -3
  3. package/package.json +7 -7
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # @niscorp/moss
2
2
 
3
+ ## 0.8.1
4
+
5
+ ### Patch Changes
6
+
7
+ - 8eaea60: The docs say where `server.checkFunctions()` goes: after every route of the app's own, before it listens.
8
+
9
+ Nobody's shell makes its reads in-process, and the server takes no route once it has answered one: a route mounted after the check throws `Can not add a route since the matcher is already built.` moss's DOCS, nisc's AGENTS and the cli README say so.
10
+
3
11
  ## 0.8.0
4
12
 
5
13
  ### Minor Changes
package/DOCS.md CHANGED
@@ -112,9 +112,14 @@ Every field is an artifact (authored data) except the code seams — `scope`,
112
112
  **`server.checkFunctions()`** builds nobody's shell once, drops it, and reads
113
113
  what its `functions(session)` returned, so what is wrong with the functions
114
114
  is refused or said before anyone is served. The app calls it once it holds
115
- the server and before it listens, as a session hook may reach for the
116
- server: `serve` of `@niscorp/moss/node` does, and so do `nisc dev`, `nisc
117
- build`, `nisc check` and `nisc start` after the project's `boot`. It says: `[moss] functions(session)
115
+ the server, as a session hook may reach for the server, after it has
116
+ mounted every route of its own, and before it listens. Nobody's shell
117
+ makes its reads in-process, and the server takes no route once it has
118
+ answered one: a route mounted after the check throws `Can not add a route
119
+ since the matcher is already built.` `serve` of `@niscorp/moss/node` calls
120
+ it, so do `nisc dev`, `nisc build` and `nisc check` after the project's
121
+ `boot`, and `nisc start` once the project's `routes` and the site are
122
+ mounted. It says: `[moss] functions(session)
118
123
  returned a map of handlers, which is deprecated: return a list of { id,
119
124
  description, execute }.`, or `[moss] functions with no description:
120
125
  auth.leave. Give each a description.` An empty description counts as none,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@niscorp/moss",
3
- "version": "0.8.0",
3
+ "version": "0.8.1",
4
4
  "description": "moss — the nisc app server: serves existence (catalog, scoped vex, the socket), derived from artifacts",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -212,11 +212,11 @@
212
212
  "zod": "^4.2.0",
213
213
  "vue": "^3.5.0",
214
214
  "vite": ">=6",
215
+ "@niscorp/prism": "^0.3.1",
215
216
  "@niscorp/charter": "^0.1.4",
216
217
  "@niscorp/strata": "^0.1.7",
217
- "@niscorp/prism": "^0.3.1",
218
- "@niscorp/nova": "^0.5.0",
219
218
  "@niscorp/tide": "^0.1.7",
219
+ "@niscorp/nova": "^0.5.0",
220
220
  "@niscorp/vex": "^0.4.1"
221
221
  },
222
222
  "peerDependenciesMeta": {
@@ -255,12 +255,12 @@
255
255
  "vitest": "^4.1.2",
256
256
  "vue": "^3.5.43",
257
257
  "zod": "^4.6.5",
258
- "@niscorp/charter": "^0.1.4",
259
- "@niscorp/prism": "^0.3.1",
260
258
  "@niscorp/strata": "^0.1.7",
261
- "@niscorp/tide": "^0.1.7",
259
+ "@niscorp/prism": "^0.3.1",
262
260
  "@niscorp/nova": "^0.5.0",
263
- "@niscorp/vex": "^0.4.1"
261
+ "@niscorp/tide": "^0.1.7",
262
+ "@niscorp/vex": "^0.4.1",
263
+ "@niscorp/charter": "^0.1.4"
264
264
  },
265
265
  "scripts": {
266
266
  "build": "node -e \"fs.rmSync('dist',{recursive:true,force:true})\" && tsup",