@lowdefy/docs-content 7.3.0 → 7.4.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/content/adapter-reference/mongodbauthadapter.md +2 -2
- package/content/agents/agent-properties.md +2 -2
- package/content/agents/agent-server-hooks.md +1 -1
- package/content/agents/agents-introduction.md +1 -1
- package/content/callback-reference/auth0logoutcallback.md +1 -1
- package/content/concepts/ai-agent-docs.md +1 -1
- package/content/concepts/blocks.md +1 -1
- package/content/concepts/connections-and-requests.md +8 -8
- package/content/concepts/custom-html.md +1 -1
- package/content/concepts/dynamic-page-content.md +1 -0
- package/content/concepts/logger.md +1 -1
- package/content/concepts/lowdefy-api.md +3 -3
- package/content/concepts/page-and-app-state.md +2 -2
- package/content/concepts/theming.md +1 -1
- package/content/connections/axioshttp.md +39 -5
- package/content/deployment/vercel.md +4 -2
- package/content/migration/v3-to-v4.md +2 -2
- package/content/operators/_ref.md +6 -6
- package/content/provider-reference/auth-js-providers.md +2 -2
- package/content/provider-reference/openidconnectprovider.md +1 -1
- package/content/tutorial/tutorial-create-page.md +1 -1
- package/content/tutorial/tutorial-requests-api.md +1 -1
- package/content/tutorial/tutorial-requests-sql.md +1 -1
- package/content/tutorial/tutorial-start.md +1 -1
- package/content/user-authentication/auth-configuration.md +9 -9
- package/content/user-authentication/protected-pages-apis.md +4 -4
- package/content/user-authentication/roles.md +2 -2
- package/content/websockets/websocket-publish.md +2 -2
- package/content/websockets/websocket-subscriptions.md +26 -1
- package/content/websockets/websockets-introduction.md +3 -2
- package/index.json +10 -10
- package/package.json +2 -2
|
@@ -18,7 +18,7 @@ If you are upgrading from the old `MongoDBAdapter`: the type is renamed, `databa
|
|
|
18
18
|
###### Minimum configuration.
|
|
19
19
|
|
|
20
20
|
```yaml
|
|
21
|
-
lowdefy: 7.
|
|
21
|
+
lowdefy: 7.4.0
|
|
22
22
|
auth:
|
|
23
23
|
database:
|
|
24
24
|
id: auth_db
|
|
@@ -31,7 +31,7 @@ auth:
|
|
|
31
31
|
###### Full configuration.
|
|
32
32
|
|
|
33
33
|
```yaml
|
|
34
|
-
lowdefy: 7.
|
|
34
|
+
lowdefy: 7.4.0
|
|
35
35
|
auth:
|
|
36
36
|
database:
|
|
37
37
|
id: auth_db
|
|
@@ -7,7 +7,7 @@ Agent properties configure the model and its behavior. They are set in the `prop
|
|
|
7
7
|
- `model: string`: __Required__ - The model identifier (e.g. `claude-sonnet-4-20250514`, `gpt-4o`, `gemini-2.5-pro`).
|
|
8
8
|
- `instructions: string`: System instructions that guide the agent's behavior. This is the system prompt sent to the model with every request. The string passes through the operator parser at request time, so `_t:` works for locale-aware prompts (see [i18n](/i18n)). Note: tool descriptions stay English — translating them can degrade tool-call accuracy on English-trained models.
|
|
9
9
|
- `pageContext: boolean`: Default: `false` - When `true`, prepend context about the current page, user, conversation, URL query, path parameters and shared state to the instructions. URL query and shared state are only included when the [`AgentChat`](/AgentChat) block sends them as `urlQuery` and `sharedState`. Path parameters, the values of the placeholders in the page's [`path`](/page-paths), are sent by the block on a page with a path, and included when there are any. Useful when the agent needs to know who it's talking to or what the user has typed into form fields.
|
|
10
|
-
- `generateTitle: boolean`: Default: `false` - When `true`, generate a short title from the first user message
|
|
10
|
+
- `generateTitle: boolean`: Default: `false` - When `true`, generate a short title from the first exchange of a conversation: the user's first message and the first 1,200 characters of the assistant's first reply. Titling from the reply means chats that open with the same suggested prompt still get titles that name their subject. The title is generated once the first reply is complete, before the response stream closes, and emitted as a `data-chat-title` data part that fires the [`AgentChat`](/AgentChat) block's `onTitleGenerated` event. A first reply that waits on a tool approval or a client tool is titled when it completes. A turn that fails is not titled, and a retry of it is. The title call uses the agent's `model`, `timeout` and `providerOptions`, so settings such as the AI Gateway's `zeroDataRetention` and `only`, OpenAI's `store` and Gemini's `safetySettings` apply to it as they do to the agent's own calls. Thinking and reasoning settings are the exception: the title call asks the model for no reasoning. A failed title generation logs a warning and does not break the turn.
|
|
11
11
|
|
|
12
12
|
###### Instructions with user context:
|
|
13
13
|
```yaml
|
|
@@ -175,7 +175,7 @@ A file in a chat or a `CallAgent` step goes to the model as a link when the prov
|
|
|
175
175
|
|
|
176
176
|
## Provider-Specific Properties
|
|
177
177
|
|
|
178
|
-
- `providerOptions: object`: Pass provider-specific options directly to the AI SDK. Use this for options not covered by the properties above.
|
|
178
|
+
- `providerOptions: object`: Pass provider-specific options directly to the AI SDK. Use this for options not covered by the properties above. These options also apply to the title call `generateTitle` makes, except thinking and reasoning settings.
|
|
179
179
|
|
|
180
180
|
Each agent type also has its own properties. See the connection pages for details:
|
|
181
181
|
|
|
@@ -108,7 +108,7 @@ api:
|
|
|
108
108
|
|
|
109
109
|
## Generating Titles
|
|
110
110
|
|
|
111
|
-
> **Built-in option:** set the agent's [`generateTitle`](/agent-properties) property to `true` and Lowdefy generates a short title from the first user message automatically, emitting the `data-chat-title` part for you. The manual approach below is only needed when you want custom title logic.
|
|
111
|
+
> **Built-in option:** set the agent's [`generateTitle`](/agent-properties) property to `true` and Lowdefy generates a short title from the first exchange (the user's first message and the assistant's first reply) automatically, emitting the `data-chat-title` part for you. The manual approach below is only needed when you want custom title logic.
|
|
112
112
|
|
|
113
113
|
Use a `data-chat-title` data part to send a generated title back to the client. The [`AgentChat`](/AgentChat) block fires an `onTitleGenerated` event when it receives this data part.
|
|
114
114
|
|
|
@@ -65,7 +65,7 @@ Agents manage the dev server with these tools, and never run `lowdefy dev`, choo
|
|
|
65
65
|
| `lowdefy_dev_stop` | Stop the app's dev server if the hub started it |
|
|
66
66
|
| `lowdefy_dev_status` | Owner, state, URL and build status, without starting anything |
|
|
67
67
|
| `lowdefy_dev_logs` | Recent output of a hub-started dev server, optionally filtered |
|
|
68
|
-
| `lowdefy_run_tests` | Run the app's journeys against its dev server, as `lowdefy test` does: all of them, a folder or glob (`paths`), or a tagged section (`tags`), narrowed by name with `filter`. Returns
|
|
68
|
+
| `lowdefy_run_tests` | Run the app's journeys against its dev server, as `lowdefy test` does: all of them, a folder or glob (`paths`), or a tagged section (`tags`), narrowed by name with `filter`. Returns a summary and the failures; all results go to `.lowdefy/test/results.json` |
|
|
69
69
|
| `lowdefy_dev_list` | Dev servers across the checkout's apps and other checkouts |
|
|
70
70
|
|
|
71
71
|
The dev server itself also serves the MCP endpoint over streamable HTTP at `/lowdefy-docs/mcp`, for clients that connect by URL. Through `lowdefy mcp`, restart is `lowdefy_dev_start` with `restart: true` rather than `lowdefy_restart`.
|
|
@@ -22,7 +22,7 @@ The schema for a Lowdefy connection is:
|
|
|
22
22
|
|
|
23
23
|
###### Connections definition example:
|
|
24
24
|
```yaml
|
|
25
|
-
lowdefy: 7.
|
|
25
|
+
lowdefy: 7.4.0
|
|
26
26
|
connections:
|
|
27
27
|
- id: connection1
|
|
28
28
|
type: ConnectionType1
|
|
@@ -100,7 +100,7 @@ _request: my_request
|
|
|
100
100
|
|
|
101
101
|
###### lowdefy.yaml
|
|
102
102
|
```yaml
|
|
103
|
-
lowdefy: 7.
|
|
103
|
+
lowdefy: 7.4.0
|
|
104
104
|
|
|
105
105
|
connections:
|
|
106
106
|
- id: connection1
|
|
@@ -142,7 +142,7 @@ To create this `connection`, define the connection as follows in the `lowdefy.ya
|
|
|
142
142
|
|
|
143
143
|
###### lowdefy.yaml
|
|
144
144
|
```yaml
|
|
145
|
-
lowdefy: 7.
|
|
145
|
+
lowdefy: 7.4.0
|
|
146
146
|
|
|
147
147
|
connections:
|
|
148
148
|
- id: my_api
|
|
@@ -159,7 +159,7 @@ To use this connection, a `request` must be defined, which references the corres
|
|
|
159
159
|
|
|
160
160
|
###### lowdefy.yaml
|
|
161
161
|
```yaml
|
|
162
|
-
lowdefy: 7.
|
|
162
|
+
lowdefy: 7.4.0
|
|
163
163
|
|
|
164
164
|
connections:
|
|
165
165
|
- id: my_api
|
|
@@ -183,7 +183,7 @@ This request should be called when the page is mounted. To do this, the [`Reques
|
|
|
183
183
|
|
|
184
184
|
###### lowdefy.yaml
|
|
185
185
|
```yaml
|
|
186
|
-
lowdefy: 7.
|
|
186
|
+
lowdefy: 7.4.0
|
|
187
187
|
|
|
188
188
|
connections:
|
|
189
189
|
- id: my_api
|
|
@@ -214,7 +214,7 @@ In this example, a [`Selector`](/Selector) block will be added. The [`_array.map
|
|
|
214
214
|
|
|
215
215
|
###### lowdefy.yaml
|
|
216
216
|
```yaml
|
|
217
|
-
lowdefy: 7.
|
|
217
|
+
lowdefy: 7.4.0
|
|
218
218
|
|
|
219
219
|
connections:
|
|
220
220
|
- id: my_api
|
|
@@ -259,7 +259,7 @@ To do this, create a new request that will make use of a `payload` to get the po
|
|
|
259
259
|
|
|
260
260
|
###### lowdefy.yaml
|
|
261
261
|
```yaml
|
|
262
|
-
lowdefy: 7.
|
|
262
|
+
lowdefy: 7.4.0
|
|
263
263
|
|
|
264
264
|
connections:
|
|
265
265
|
- id: my_api
|
|
@@ -321,7 +321,7 @@ This is done as follows:
|
|
|
321
321
|
|
|
322
322
|
###### lowdefy.yaml
|
|
323
323
|
```yaml
|
|
324
|
-
lowdefy: 7.
|
|
324
|
+
lowdefy: 7.4.0
|
|
325
325
|
|
|
326
326
|
connections:
|
|
327
327
|
- id: my_api
|
|
@@ -246,6 +246,7 @@ The policy checks a value as a URL where it is used as a link or a source: `href
|
|
|
246
246
|
Everywhere else a URL is plain text:
|
|
247
247
|
|
|
248
248
|
- **Text a block draws.** A block's properties schema marks how it draws a string (`textKind`). In a property it draws as HTML, such as a `Descriptions` item value, a `Paragraph` content, an input `title` or a `Selector` option label, a whole URL, a markdown link, a word starting with `//` and (unless the policy allows HTML) a CSS `url()` are words, since nothing there reads them as a link. The `html` rule still applies there, so text a block draws as HTML shows as written only when it is HTML-escaped (`<` for `<`, `&` for `&`). In a property it draws as escaped text, such as a `ControlledList` title, tag syntax is words too. When the policy allows HTML, a link or source attribute (`href`, `src`, `srcset`) in any string not drawn as escaped text is judged as a link or source, as a `url` or `src` property is.
|
|
249
|
+
- **Object keys and slot names.** A block can draw a key as well as a value: the keys of a `Descriptions` `items` object are its labels, and `Tabs` and `Collapse` draw slot names as titles. No schema marks how a key is drawn, so every object key and every slot or area name keeps every check a string no schema marks gets: the `html` rule and every URL check. Keys in data are not checked, since data is never drawn.
|
|
249
250
|
- **State.** When the policy sets a `state` path, `SetState` values, such as a form's prefill, are data: no block property can read state (properties are literal). A URL or tag syntax in them is text, and only the operator rules apply. Without a `state` path the content may write any page state, so its `SetState` values keep every check. A value bound to an input in the content whose value is an object, such as a rich text editor, an upload or a table input, keeps every check, since those inputs draw parts of their value as markup, links or images. The content may read data state (`SetState` values, and the state of an input whose option values or rows are data) only in a `CallAPI`'s params, an action's `skip`, a `SetState` value, or an `:if` or `:case` condition. A `_state` read of it anywhere else, such as a `DisplayMessage`'s content, fails with `policy.state`. The page around the Dynamic block owns the state under the policy's `state` path: anything there that draws it as HTML or follows it as a link must treat it as untrusted input, whatever the policy's `html` setting.
|
|
250
251
|
- **Option values.** A `Selector` or `MultipleSelector` option `value` beside a `label` is data (`textKind: data`); the `label` is drawn as HTML. An option without a `label` draws its `value` as HTML in its place, so that value keeps every check.
|
|
251
252
|
- **Table cells.** When every column of a `Table` or `TableLight` draws its cell as text (`text`, `email`, `phone`, `number`, `currency`, `percent`, `progress`, `rating`, `date`, `datetime`, `boolean`, `tag`, `tags`, `status` or `json`, or no type), its `data` rows are data. A `url`, `link`, `relation`, `image`, `avatar`, `people`, `html`, `buttons` or `menu` column draws or follows row values, a `cell.colorFrom` reads a row field into a colour, and an `expandable.template` draws row fields as HTML, so their table's rows keep every check.
|
|
@@ -42,7 +42,7 @@ The schema for a Lowdefy API is:
|
|
|
42
42
|
###### API definition example:
|
|
43
43
|
|
|
44
44
|
```yaml
|
|
45
|
-
lowdefy: '7.
|
|
45
|
+
lowdefy: '7.4.0'
|
|
46
46
|
|
|
47
47
|
connections:
|
|
48
48
|
- id: users
|
|
@@ -77,7 +77,7 @@ Lowdefy APIs use the same [authorization configuration](/protected-pages-apis) a
|
|
|
77
77
|
Unlike requests which are defined on a specific page and inherit the authorization of the page they are defined on, API endpoints can be called from any page in the app. Thus they do not inherit the authorization of the page they are called from, and authorization should be configured separately.
|
|
78
78
|
|
|
79
79
|
```yaml
|
|
80
|
-
lowdefy: '7.
|
|
80
|
+
lowdefy: '7.4.0'
|
|
81
81
|
|
|
82
82
|
auth:
|
|
83
83
|
# Configure which APIs require authentication
|
|
@@ -1235,7 +1235,7 @@ blocks:
|
|
|
1235
1235
|
Here's a comprehensive example showing various features:
|
|
1236
1236
|
|
|
1237
1237
|
```yaml
|
|
1238
|
-
lowdefy: '7.
|
|
1238
|
+
lowdefy: '7.4.0'
|
|
1239
1239
|
auth:
|
|
1240
1240
|
api:
|
|
1241
1241
|
protected: true
|
|
@@ -83,7 +83,7 @@ This example shows how you can create and read from `global`:
|
|
|
83
83
|
|
|
84
84
|
`lowdefy.yaml`
|
|
85
85
|
```yaml
|
|
86
|
-
lowdefy: 7.
|
|
86
|
+
lowdefy: 7.4.0
|
|
87
87
|
global:
|
|
88
88
|
key: value
|
|
89
89
|
pages:
|
|
@@ -101,7 +101,7 @@ The following examples shows how to modify the `global` object:
|
|
|
101
101
|
|
|
102
102
|
`lowdefy.yaml`
|
|
103
103
|
```yaml
|
|
104
|
-
lowdefy: 7.
|
|
104
|
+
lowdefy: 7.4.0
|
|
105
105
|
global:
|
|
106
106
|
key: value
|
|
107
107
|
pages:
|
|
@@ -4,10 +4,41 @@ The `AxiosHttp` connection is used to connect to APIs and web servers using HTTP
|
|
|
4
4
|
|
|
5
5
|
It uses the [axios](https://github.com/axios/axios) library.
|
|
6
6
|
|
|
7
|
-
|
|
7
|
+
Most properties can be set on both connections and requests. The properties will be merged, with the request properties overwriting connection properties. This allows properties like authentication headers and the baseURL to be set on the connection, with request specific properties like the request. The properties that decide where the server may connect (`allowInternalAddresses`, `allowedHosts`, `allowAbsoluteUrls`, `proxy`, `socketPath`, `httpVersion`, `httpAgentOptions` and `httpsAgentOptions`) can only be set on the connection, since request properties can be filled from the client payload.
|
|
8
8
|
|
|
9
9
|
>Secrets like authentication headers and API keys should be stored using the [`_secret`](_secret) operator.
|
|
10
10
|
|
|
11
|
+
## Internal addresses
|
|
12
|
+
|
|
13
|
+
By default, `AxiosHttp` only connects to public addresses. A request to localhost, a private network (`10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16`), a link-local address such as the cloud metadata endpoint `169.254.169.254`, or another address that is not public, fails. A hostname is checked by the address it resolves to, and every redirect is checked too.
|
|
14
|
+
|
|
15
|
+
This matters when a request takes its URL, or part of it, from the payload. Without the check, a user could point the request at a service the server can reach but the internet cannot, such as a database admin page or the cloud metadata endpoint, which hands out the server's cloud credentials.
|
|
16
|
+
|
|
17
|
+
To call a service on the same machine or network, such as an API on localhost, a Docker Compose service name or an API on a private network, set `allowInternalAddresses: true` on the connection:
|
|
18
|
+
|
|
19
|
+
```yaml
|
|
20
|
+
connections:
|
|
21
|
+
- id: orders_service
|
|
22
|
+
type: AxiosHttp
|
|
23
|
+
properties:
|
|
24
|
+
baseURL: http://orders-service:8080
|
|
25
|
+
allowInternalAddresses: true
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
Without `allowInternalAddresses`, the server connects directly: the `HTTP_PROXY` and `HTTPS_PROXY` environment variables are ignored, and `proxy`, `socketPath` and `httpVersion: 2` fail, since the server cannot check where they connect.
|
|
29
|
+
|
|
30
|
+
To limit a connection to known hosts, list them in `allowedHosts`. A request to any other host, or a redirect to one, fails. `allowedHosts` applies alongside the address check: an internal host must be listed and the connection must set `allowInternalAddresses: true`.
|
|
31
|
+
|
|
32
|
+
```yaml
|
|
33
|
+
connections:
|
|
34
|
+
- id: partner_api
|
|
35
|
+
type: AxiosHttp
|
|
36
|
+
properties:
|
|
37
|
+
baseURL: https://api.partner.com
|
|
38
|
+
allowedHosts:
|
|
39
|
+
- api.partner.com
|
|
40
|
+
```
|
|
41
|
+
|
|
11
42
|
## Connections
|
|
12
43
|
|
|
13
44
|
Connection types:
|
|
@@ -38,14 +69,17 @@ Request types:
|
|
|
38
69
|
- `auth: object`: Indicates that HTTP Basic authorization should be used, and supplies credentials. This will set an `Authorization` header, overwriting any existing `Authorization` custom headers you have set using `headers`. Only HTTP Basic auth is configurable through this parameter, for Bearer tokens and such, use `Authorization` custom headers instead. The `auth` object should have the following fields:
|
|
39
70
|
- `username: string`
|
|
40
71
|
- `password: string`
|
|
41
|
-
- `
|
|
42
|
-
- `
|
|
72
|
+
- `allowInternalAddresses: boolean`: Default: `false` - Connection only. Allow requests to addresses that are not public, such as localhost, private networks and the cloud metadata endpoint. Also needed for `proxy`, `socketPath` and `httpVersion: 2`. See [Internal addresses](#internal-addresses).
|
|
73
|
+
- `allowedHosts: string[]`: Connection only. The hostnames requests may connect to, matched exactly and ignoring case (no wildcards or ports). A request to any other host, or a redirect to one, fails.
|
|
74
|
+
- `httpAgentOptions: object`: Connection only. Options to pass to the Node.js [`http.Agent`](https://nodejs.org/api/http.html#http_class_http_agent) class.
|
|
75
|
+
- `httpsAgentOptions: object`: Connection only. Options to pass to the Node.js [`https.Agent`](https://nodejs.org/api/http.html#http_class_http_agent) class.
|
|
43
76
|
- `maxContentLength: number`: Defines the max size of the http response content allowed in bytes.
|
|
44
77
|
- `maxRedirects: number`: Defines the maximum number of redirects to follow. If set to 0, no redirects will be followed.
|
|
45
|
-
- `proxy: object`: Defines the hostname and port of the proxy server. The `proxy` object should have the following fields:
|
|
78
|
+
- `proxy: object`: Connection only, and needs `allowInternalAddresses: true`. Defines the hostname and port of the proxy server. The `proxy` object should have the following fields:
|
|
46
79
|
- `host: string`: Host IP address (eg. `'127.0.0.1'`).
|
|
47
80
|
- `port: number`: Port number.
|
|
48
81
|
- `auth: object`: Object with username and password.
|
|
82
|
+
- `socketPath: string`: Connection only, and needs `allowInternalAddresses: true`. A Unix socket to send requests to instead of a host.
|
|
49
83
|
- `responseType: enum`: Default: `'json'` - The type of data that the server will respond with. Options are:
|
|
50
84
|
- `'document'`
|
|
51
85
|
- `'json'`
|
|
@@ -64,7 +98,7 @@ Properties for a AxiosHttp can be set on either the connection, the request, or
|
|
|
64
98
|
###### A basic full example requesting data from https://jsonplaceholder.typicode.com
|
|
65
99
|
|
|
66
100
|
```yaml
|
|
67
|
-
lowdefy: 7.
|
|
101
|
+
lowdefy: 7.4.0
|
|
68
102
|
name: Lowdefy starter
|
|
69
103
|
connections:
|
|
70
104
|
- id: my_api
|
|
@@ -50,7 +50,7 @@ config:
|
|
|
50
50
|
memory: 2048 # MB — omit to use the Vercel default
|
|
51
51
|
```
|
|
52
52
|
|
|
53
|
-
- **`maxDuration`** — the hard cap on function execution time, in seconds. Defaults to `60`. Your plan's limits apply; Vercel rejects an over-limit value at deploy time.
|
|
53
|
+
- **`maxDuration`** — the hard cap on function execution time, in seconds. Defaults to `60`. Your plan's limits apply; Vercel rejects an over-limit value at deploy time. It also bounds each websocket connection: the server closes it 5 seconds before the limit and the client reconnects.
|
|
54
54
|
- **`memory`** — function memory in MB. Omit to use the Vercel default.
|
|
55
55
|
|
|
56
56
|
Each build writes these into the generated `.vercel/output/functions/api.func/.vc-config.json`. The output is regenerated on every deploy, so there is nothing to edit by hand — and because the deployment is prebuilt (Build Output API), `functions` settings in `vercel.json` or the dashboard's function defaults do not apply; `lowdefy.yaml` is the single source of truth.
|
|
@@ -119,8 +119,10 @@ Vercel Fluid bills by execution duration, so a request that hangs (a stuck datab
|
|
|
119
119
|
|
|
120
120
|
Keep `config.requestTimeout` below `maxDuration`: when it is not, Vercel stops the function before the request timeout answers, so the upstream calls the request left running are not cancelled and the request ends without a logged timeout. The build warns when `config.requestTimeout` is not shorter than `maxDuration` (or than the 60-second default, when it runs on Vercel).
|
|
121
121
|
|
|
122
|
+
Give each agent a `timeout` below `maxDuration`, on the agent or on its connection. A chat turn is exempt from `config.requestTimeout` and runs on after its client disconnects, so without one only `maxDuration` stops it: the stream then ends without an error and the agent's `onFinish` hooks, which save the conversation, never run. The build warns for an agent with no timeout, or with one not shorter than `maxDuration`.
|
|
123
|
+
|
|
122
124
|
On Vercel, only the request timeout cancels an AI model call a request is waiting on. A client that disconnects does not: the call runs until it finishes, reaches its own `timeout`, or hits the request timeout. On the Node server a disconnect cancels it too.
|
|
123
125
|
|
|
124
|
-
> The function runs on Vercel's Node.js runtime. Streaming agent responses (`/api/agent/*`) are exempt from `config.requestTimeout` and are bounded
|
|
126
|
+
> The function runs on Vercel's Node.js runtime. Streaming agent responses (`/api/agent/*`) are exempt from `config.requestTimeout` and are bounded by the agent's own `timeout` and `maxDuration` — for heavy streaming or agent workloads, a long-lived Node host (Docker, Fly.io, Railway, Render) may suit better. An agent run keeps running to the end when its client disconnects, so its work completes; a `GET` stream (such as an SSE feed) stops when its client goes, instead of holding the function until `maxDuration`. The MCP endpoint answers `GET` with 405, so an MCP client holds no stream open.
|
|
125
127
|
|
|
126
128
|
All other Vercel configuration like domain names, preview deploy branches, serverless regions and redirects can be configured as desired.
|
|
@@ -363,7 +363,7 @@ blocks:
|
|
|
363
363
|
The `LOWDEFY_SERVER_BASE_PATH` environment variable configuration option has been removed. To configure a base path, use the `config.basePath` configuration option.
|
|
364
364
|
|
|
365
365
|
``yaml
|
|
366
|
-
lowdefy: 7.
|
|
366
|
+
lowdefy: 7.4.0
|
|
367
367
|
|
|
368
368
|
config:
|
|
369
369
|
basePath: /foo
|
|
@@ -371,7 +371,7 @@ config:
|
|
|
371
371
|
|
|
372
372
|
The `_build.env` operator can be used to set the base path using an environment variable:
|
|
373
373
|
```yaml
|
|
374
|
-
lowdefy: 7.
|
|
374
|
+
lowdefy: 7.4.0
|
|
375
375
|
|
|
376
376
|
config:
|
|
377
377
|
basePath:
|
|
@@ -82,7 +82,7 @@ The file path to the referenced file, from the root of the project directory.
|
|
|
82
82
|
###### Reference pages:
|
|
83
83
|
```yaml
|
|
84
84
|
# lowdefy.yaml
|
|
85
|
-
lowdefy: 7.
|
|
85
|
+
lowdefy: 7.4.0
|
|
86
86
|
pages:
|
|
87
87
|
- _ref: pages/page1.yaml
|
|
88
88
|
- _ref: pages/page2.yaml
|
|
@@ -103,7 +103,7 @@ blocks:
|
|
|
103
103
|
```
|
|
104
104
|
Returns:
|
|
105
105
|
```
|
|
106
|
-
lowdefy: 7.
|
|
106
|
+
lowdefy: 7.4.0
|
|
107
107
|
pages:
|
|
108
108
|
- id: page1
|
|
109
109
|
type: PageHeaderMenu
|
|
@@ -176,7 +176,7 @@ blocks:
|
|
|
176
176
|
###### Use key:
|
|
177
177
|
```yaml
|
|
178
178
|
# lowdefy.yaml
|
|
179
|
-
lowdefy: 7.
|
|
179
|
+
lowdefy: 7.4.0
|
|
180
180
|
version:
|
|
181
181
|
_ref:
|
|
182
182
|
path: package.json
|
|
@@ -190,7 +190,7 @@ version:
|
|
|
190
190
|
```
|
|
191
191
|
Returns:
|
|
192
192
|
```
|
|
193
|
-
lowdefy: 7.
|
|
193
|
+
lowdefy: 7.4.0
|
|
194
194
|
version: 1.0.0
|
|
195
195
|
```
|
|
196
196
|
|
|
@@ -227,7 +227,7 @@ module.exports = useLocalOrSharedConfig;
|
|
|
227
227
|
|
|
228
228
|
```yaml
|
|
229
229
|
// lowdefy.yaml
|
|
230
|
-
lowdefy: 7.
|
|
230
|
+
lowdefy: 7.4.0
|
|
231
231
|
|
|
232
232
|
cli:
|
|
233
233
|
refResolver: resolvers/useLocalOrSharedConfig.js
|
|
@@ -253,7 +253,7 @@ module.exports = addFooter;
|
|
|
253
253
|
```
|
|
254
254
|
```yaml
|
|
255
255
|
// lowdefy.yaml
|
|
256
|
-
lowdefy: 7.
|
|
256
|
+
lowdefy: 7.4.0
|
|
257
257
|
|
|
258
258
|
pages:
|
|
259
259
|
- _ref:
|
|
@@ -75,7 +75,7 @@ The providers that can be used are:
|
|
|
75
75
|
###### Auth0 configuration:
|
|
76
76
|
|
|
77
77
|
```yaml
|
|
78
|
-
lowdefy: 7.
|
|
78
|
+
lowdefy: 7.4.0
|
|
79
79
|
auth:
|
|
80
80
|
providers:
|
|
81
81
|
- id: auth0
|
|
@@ -94,7 +94,7 @@ In Auth0, the callback URL should be configured to `https://example.com/api/auth
|
|
|
94
94
|
###### GitHub configuration:
|
|
95
95
|
|
|
96
96
|
```yaml
|
|
97
|
-
lowdefy: 7.
|
|
97
|
+
lowdefy: 7.4.0
|
|
98
98
|
auth:
|
|
99
99
|
providers:
|
|
100
100
|
- id: github
|
|
@@ -28,7 +28,7 @@ The OpenIDConnectProvider can be used to authenticate with a OpenID Connect comp
|
|
|
28
28
|
Usually only the `wellKnown`, `clientId` and `clientSecret` properties need to be configured:
|
|
29
29
|
|
|
30
30
|
```yaml
|
|
31
|
-
lowdefy: 7.
|
|
31
|
+
lowdefy: 7.4.0
|
|
32
32
|
providers:
|
|
33
33
|
- id: my_provider
|
|
34
34
|
type: OpenIDConnectProvider
|
|
@@ -63,7 +63,7 @@ Made by a Lowdefy 🤖
|
|
|
63
63
|
Open the `lowdefy.yaml` file using a text editor like [VS Code](https://code.visualstudio.com/download). The content of the file should look like this:
|
|
64
64
|
|
|
65
65
|
```yaml
|
|
66
|
-
lowdefy: 7.
|
|
66
|
+
lowdefy: 7.4.0
|
|
67
67
|
name: Lowdefy starter
|
|
68
68
|
|
|
69
69
|
pages:
|
|
@@ -11,7 +11,7 @@ For a login method to work you must configure **at least one mechanism** (`email
|
|
|
11
11
|
A required signing secret, given as a `_secret` reference:
|
|
12
12
|
|
|
13
13
|
```yaml
|
|
14
|
-
lowdefy: 7.
|
|
14
|
+
lowdefy: 7.4.0
|
|
15
15
|
auth:
|
|
16
16
|
secret:
|
|
17
17
|
_secret: BETTER_AUTH_SECRET
|
|
@@ -24,7 +24,7 @@ Also pin the app's canonical origin — the `url` of the current environment in
|
|
|
24
24
|
Sessions, users, accounts and organizations are stored through an adapter:
|
|
25
25
|
|
|
26
26
|
```yaml
|
|
27
|
-
lowdefy: 7.
|
|
27
|
+
lowdefy: 7.4.0
|
|
28
28
|
auth:
|
|
29
29
|
database:
|
|
30
30
|
id: auth_db
|
|
@@ -46,7 +46,7 @@ See the [MongoDBAuthAdapter](/MongoDBAuthAdapter) reference. Collection names fo
|
|
|
46
46
|
- **Passkeys** — `auth.passkey` (`enabled`, `rpId`, `rpName`).
|
|
47
47
|
|
|
48
48
|
```yaml
|
|
49
|
-
lowdefy: 7.
|
|
49
|
+
lowdefy: 7.4.0
|
|
50
50
|
auth:
|
|
51
51
|
emailAndPassword:
|
|
52
52
|
enabled: true
|
|
@@ -58,7 +58,7 @@ auth:
|
|
|
58
58
|
`auth.email` references an **SMTP connection** by id — the connection owns `from`, `replyTo`, the transport and the delivery filter, and is shared by every auth email flow. There is no inline transport shape. Optionally map individual flows to your own notification templates:
|
|
59
59
|
|
|
60
60
|
```yaml
|
|
61
|
-
lowdefy: 7.
|
|
61
|
+
lowdefy: 7.4.0
|
|
62
62
|
auth:
|
|
63
63
|
email:
|
|
64
64
|
connectionId: email # an SMTP connection in connections[]
|
|
@@ -94,7 +94,7 @@ BetterAuth ships no UI — your app owns its auth pages, and `auth.authPages` po
|
|
|
94
94
|
| `magicLink` | — | landing page for the sign-in email (opt-in; see below) |
|
|
95
95
|
|
|
96
96
|
```yaml
|
|
97
|
-
lowdefy: 7.
|
|
97
|
+
lowdefy: 7.4.0
|
|
98
98
|
auth:
|
|
99
99
|
authPages:
|
|
100
100
|
signIn: /login
|
|
@@ -113,7 +113,7 @@ A verification email links to Better Auth's verify endpoint, which confirms the
|
|
|
113
113
|
Set the key and the sign-in email links to a page of your own instead, with the token and the callback destinations carried on its URL query. Fetching a Lowdefy page is harmless, so the token stays unspent until a real click runs [`MagicLinkVerify`](/MagicLinkVerify):
|
|
114
114
|
|
|
115
115
|
```yaml
|
|
116
|
-
lowdefy: 7.
|
|
116
|
+
lowdefy: 7.4.0
|
|
117
117
|
auth:
|
|
118
118
|
magicLink:
|
|
119
119
|
enabled: true
|
|
@@ -161,7 +161,7 @@ See [Two-Factor Authentication](/two-factor) for the two-factor pages, and the [
|
|
|
161
161
|
Database sessions. Length is `expiresIn` (seconds, default 604800 = 7 days); `updateAge` (default 86400) is how often an active session's expiry is refreshed:
|
|
162
162
|
|
|
163
163
|
```yaml
|
|
164
|
-
lowdefy: 7.
|
|
164
|
+
lowdefy: 7.4.0
|
|
165
165
|
auth:
|
|
166
166
|
session:
|
|
167
167
|
expiresIn: 43200 # 12 hours in seconds
|
|
@@ -177,7 +177,7 @@ auth:
|
|
|
177
177
|
- **API strategies** — `auth.strategies` authenticates non-session callers (server-to-server) with an `apiKey` or a `jwt`:
|
|
178
178
|
|
|
179
179
|
```yaml
|
|
180
|
-
lowdefy: 7.
|
|
180
|
+
lowdefy: 7.4.0
|
|
181
181
|
auth:
|
|
182
182
|
strategies:
|
|
183
183
|
- id: service-key
|
|
@@ -231,7 +231,7 @@ Add the `auth.dev.mockUser` section to your `lowdefy.yaml`:
|
|
|
231
231
|
|
|
232
232
|
###### Configure a mock user for development
|
|
233
233
|
```yaml
|
|
234
|
-
lowdefy: 7.
|
|
234
|
+
lowdefy: 7.4.0
|
|
235
235
|
|
|
236
236
|
auth:
|
|
237
237
|
providers:
|
|
@@ -14,7 +14,7 @@ The 404 page (used to indicate that a requested page cannot be found) is always
|
|
|
14
14
|
|
|
15
15
|
###### List specific public pages and APIs:
|
|
16
16
|
```yaml
|
|
17
|
-
lowdefy: 7.
|
|
17
|
+
lowdefy: 7.4.0
|
|
18
18
|
auth:
|
|
19
19
|
pages:
|
|
20
20
|
protected: true
|
|
@@ -31,7 +31,7 @@ auth:
|
|
|
31
31
|
|
|
32
32
|
###### List specific protected pages and APIs:
|
|
33
33
|
```yaml
|
|
34
|
-
lowdefy: 7.
|
|
34
|
+
lowdefy: 7.4.0
|
|
35
35
|
auth:
|
|
36
36
|
pages:
|
|
37
37
|
public: true
|
|
@@ -47,7 +47,7 @@ auth:
|
|
|
47
47
|
|
|
48
48
|
###### Mixed configuration:
|
|
49
49
|
```yaml
|
|
50
|
-
lowdefy: 7.
|
|
50
|
+
lowdefy: 7.4.0
|
|
51
51
|
auth:
|
|
52
52
|
# Protect specific pages while keeping most public
|
|
53
53
|
pages:
|
|
@@ -75,7 +75,7 @@ Exact page IDs still work: `home`, `team-users/users-list`.
|
|
|
75
75
|
|
|
76
76
|
###### Wildcard pattern example:
|
|
77
77
|
```yaml
|
|
78
|
-
lowdefy: 7.
|
|
78
|
+
lowdefy: 7.4.0
|
|
79
79
|
auth:
|
|
80
80
|
pages:
|
|
81
81
|
protected: true
|
|
@@ -7,7 +7,7 @@ Roles are read from the `roles` field on the [user object](/user-object) — an
|
|
|
7
7
|
Declare the role names your app uses in `auth.roles` (id, optional label and description) so tooling can list them:
|
|
8
8
|
|
|
9
9
|
```yaml
|
|
10
|
-
lowdefy: 7.
|
|
10
|
+
lowdefy: 7.4.0
|
|
11
11
|
auth:
|
|
12
12
|
roles:
|
|
13
13
|
- id: user-admin
|
|
@@ -24,7 +24,7 @@ Similarly, the API endpoints that are protected by roles are configured in the `
|
|
|
24
24
|
|
|
25
25
|
###### Protect pages and API endpoints using roles:
|
|
26
26
|
```yaml
|
|
27
|
-
lowdefy: 7.
|
|
27
|
+
lowdefy: 7.4.0
|
|
28
28
|
auth:
|
|
29
29
|
pages:
|
|
30
30
|
public: true
|
|
@@ -5,7 +5,7 @@ A `Channel` websocket relays messages between clients: any subscriber can publis
|
|
|
5
5
|
## A Minimal Chat
|
|
6
6
|
|
|
7
7
|
```yaml
|
|
8
|
-
lowdefy: 7.
|
|
8
|
+
lowdefy: 7.4.0
|
|
9
9
|
|
|
10
10
|
websockets:
|
|
11
11
|
- id: team_chat
|
|
@@ -97,7 +97,7 @@ Page `subscriptions` cover most cases, but the actions give dynamic control —
|
|
|
97
97
|
|
|
98
98
|
Websockets use Vercel's native WebSocket support for Node.js functions on Fluid compute — deploy the same project, no configuration. Two platform behaviors to know:
|
|
99
99
|
|
|
100
|
-
- Connections close when a function reaches its `maxDuration`. The Lowdefy client reconnects and resubscribes
|
|
100
|
+
- Connections close when a function reaches its `maxDuration`. The server closes each connection 5 seconds before then (at half the limit when it is under 10 seconds), and the Lowdefy client reconnects and resubscribes at once. Changes a source publishes during the reconnect are not delivered; raise `maxDuration` to reduce reconnect frequency on websocket-heavy apps.
|
|
101
101
|
- Under load, Vercel may run multiple instances of your app. Server-driven sources run per instance, so every subscriber receives every source message regardless of which instance they land on. Client publishes, however, reach subscribers connected to the same instance. For chat-style apps at multi-instance scale, a cross-instance pubsub adapter is on the roadmap.
|
|
102
102
|
|
|
103
103
|
### Self-Hosted
|
|
@@ -52,7 +52,32 @@ events:
|
|
|
52
52
|
_event: messages # array of message payloads in this batch
|
|
53
53
|
```
|
|
54
54
|
|
|
55
|
-
`onSubscribe` fires when the server acknowledges the subscription
|
|
55
|
+
`onSubscribe` fires when the server acknowledges the subscription, again after an automatic reconnect, and again when the channel's source is back after an outage. `onError` fires with `_event: message` when the channel errors.
|
|
56
|
+
|
|
57
|
+
## When the Source Fails
|
|
58
|
+
|
|
59
|
+
A channel's source can fail while pages are subscribed, for example when the database is unreachable. The page stays subscribed and the server restarts the source for as long as anyone is subscribed: 1 second after the failure, then doubling up to once a minute.
|
|
60
|
+
|
|
61
|
+
- During the outage, each failed start sends the page an error: `onError` fires and `_websocket: <id>.error` holds the message. No messages arrive, and the source misses whatever changes in the meantime.
|
|
62
|
+
- When the source is listening again, `onSubscribe` fires, `error` returns to `null` and messages flow again.
|
|
63
|
+
|
|
64
|
+
So a page that refetches in `onSubscribe` as well as in `onMessage` also catches up after an outage and after a reconnect:
|
|
65
|
+
|
|
66
|
+
```yaml
|
|
67
|
+
subscriptions:
|
|
68
|
+
- websocketId: order_updates
|
|
69
|
+
events:
|
|
70
|
+
onSubscribe:
|
|
71
|
+
- id: refetch
|
|
72
|
+
type: Request
|
|
73
|
+
params: get_orders
|
|
74
|
+
onMessage:
|
|
75
|
+
- id: refetch
|
|
76
|
+
type: Request
|
|
77
|
+
params: get_orders
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
The server reports the outage's first failure as an error, to the log and Sentry, and each further failed restart as a warning.
|
|
56
81
|
|
|
57
82
|
## Reading Channel State with `_websocket`
|
|
58
83
|
|
|
@@ -9,7 +9,7 @@ Websockets work identically on a self-hosted Node.js server and on Vercel, where
|
|
|
9
9
|
A channel and a page subscription — this page shows a live tick counter:
|
|
10
10
|
|
|
11
11
|
```yaml
|
|
12
|
-
lowdefy: 7.
|
|
12
|
+
lowdefy: 7.4.0
|
|
13
13
|
|
|
14
14
|
websockets:
|
|
15
15
|
- id: ticker
|
|
@@ -41,8 +41,9 @@ When the page loads, the client opens a websocket connection, subscribes to `tic
|
|
|
41
41
|
3. The server authorizes the subscription against the channel's `auth` config and, when the websocket has a `check`, calls the check endpoint as the subscriber. It then evaluates the websocket `properties` server-side — `_payload` reads the subscription payload and `_user` reads the subscriber's session, so a channel can be user-specific.
|
|
42
42
|
4. Subscribers whose evaluated properties are identical share one running source on the server. The first subscriber starts it; the last one to leave stops it.
|
|
43
43
|
5. Messages from the source are pushed to all subscribers, update the channel state read by the [`_websocket`](/websocket-subscriptions) operator, and fire the subscription's `onMessage` event.
|
|
44
|
+
6. If the source fails, for example during a database outage, the server restarts it for as long as the channel has subscribers, up to once a minute. Subscribers get an `onError` for each failed start, and `onSubscribe` when the source is listening again, so the page can refetch what it missed. See [When the Source Fails](/websocket-subscriptions#when-the-source-fails).
|
|
44
45
|
|
|
45
|
-
If the connection drops — a deploy, a network blip, or a serverless function reaching its time limit — the client reconnects with backoff and resubscribes automatically. Channel state on the page is preserved across reconnects.
|
|
46
|
+
If the connection drops — a deploy, a network blip, or a serverless function reaching its time limit — the client reconnects with backoff and resubscribes automatically. Channel state on the page is preserved across reconnects. On Vercel the server closes each connection 5 seconds before the function's `maxDuration`, so the client reconnects at once instead of noticing the dead connection about 10 seconds late.
|
|
46
47
|
|
|
47
48
|
## Websocket Definition
|
|
48
49
|
|
package/index.json
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "7.
|
|
2
|
+
"version": "7.4.0",
|
|
3
3
|
"docs": [
|
|
4
4
|
{
|
|
5
5
|
"slug": "learn/introduction",
|
|
@@ -3113,14 +3113,14 @@
|
|
|
3113
3113
|
"concepts/advanced/dynamic-page-content.yaml",
|
|
3114
3114
|
"version.yaml"
|
|
3115
3115
|
],
|
|
3116
|
-
"hash": "
|
|
3116
|
+
"hash": "80eac384292186530102446d68826d1c0be59dc66241c8dfc44e6e19b27035c3"
|
|
3117
3117
|
},
|
|
3118
3118
|
"concepts/ai-agent-docs": {
|
|
3119
3119
|
"files": [
|
|
3120
3120
|
"concepts/advanced/ai-agent-docs.md",
|
|
3121
3121
|
"concepts/advanced/ai-agent-docs.yaml"
|
|
3122
3122
|
],
|
|
3123
|
-
"hash": "
|
|
3123
|
+
"hash": "67982e5e01dfa11e4591ba3569a8bf5df6f97f7c0f6557dff3e3bca209600e69"
|
|
3124
3124
|
},
|
|
3125
3125
|
"agents/agents-introduction": {
|
|
3126
3126
|
"files": [
|
|
@@ -3133,7 +3133,7 @@
|
|
|
3133
3133
|
"files": [
|
|
3134
3134
|
"agents/agent-properties.yaml"
|
|
3135
3135
|
],
|
|
3136
|
-
"hash": "
|
|
3136
|
+
"hash": "5f6778173d5ce47f50b5098ec59859916da99e953ac89d84cecebdaacb7c2304"
|
|
3137
3137
|
},
|
|
3138
3138
|
"agents/agent-endpoint-tools": {
|
|
3139
3139
|
"files": [
|
|
@@ -3157,7 +3157,7 @@
|
|
|
3157
3157
|
"files": [
|
|
3158
3158
|
"agents/server-hooks.yaml"
|
|
3159
3159
|
],
|
|
3160
|
-
"hash": "
|
|
3160
|
+
"hash": "9a4b2d0c867bbb31e6b9d2936354a6aa786187b0f33826ff83eca73e0429f20b"
|
|
3161
3161
|
},
|
|
3162
3162
|
"agents/agentchat": {
|
|
3163
3163
|
"files": [
|
|
@@ -3176,21 +3176,21 @@
|
|
|
3176
3176
|
"version.yaml",
|
|
3177
3177
|
"websockets/introduction.yaml"
|
|
3178
3178
|
],
|
|
3179
|
-
"hash": "
|
|
3179
|
+
"hash": "4cb3dcf88d3a35109f92c6d6c1fcb7ca6d4257f291f659014e378c90a760d4a0"
|
|
3180
3180
|
},
|
|
3181
3181
|
"websockets/websocket-subscriptions": {
|
|
3182
3182
|
"files": [
|
|
3183
3183
|
"version.yaml",
|
|
3184
3184
|
"websockets/subscriptions.yaml"
|
|
3185
3185
|
],
|
|
3186
|
-
"hash": "
|
|
3186
|
+
"hash": "5ac50cfa0c54160632bf1de3b2a8ca95adb32232ca5252431e0d1fe15b273870"
|
|
3187
3187
|
},
|
|
3188
3188
|
"websockets/websocket-publish": {
|
|
3189
3189
|
"files": [
|
|
3190
3190
|
"version.yaml",
|
|
3191
3191
|
"websockets/publish.yaml"
|
|
3192
3192
|
],
|
|
3193
|
-
"hash": "
|
|
3193
|
+
"hash": "e01f81f52a3bff3493e3f31b2a43fc9e9cb93a13bb3821e5befe9666100ec1fe"
|
|
3194
3194
|
},
|
|
3195
3195
|
"deployment/docker": {
|
|
3196
3196
|
"files": [
|
|
@@ -3208,7 +3208,7 @@
|
|
|
3208
3208
|
"files": [
|
|
3209
3209
|
"deployment/vercel.yaml"
|
|
3210
3210
|
],
|
|
3211
|
-
"hash": "
|
|
3211
|
+
"hash": "a3d55236b70520fe05204231204e92c0e192e2d0588f9fc8a40c1711c5fc776c"
|
|
3212
3212
|
},
|
|
3213
3213
|
"deployment/deployment-environments": {
|
|
3214
3214
|
"files": [
|
|
@@ -4874,7 +4874,7 @@
|
|
|
4874
4874
|
"connections/AxiosHttp.yaml",
|
|
4875
4875
|
"version.yaml"
|
|
4876
4876
|
],
|
|
4877
|
-
"hash": "
|
|
4877
|
+
"hash": "6dc718d4c360b78d0cc5d50b0af63b3502185b68a47defa206185b51e8f7597a"
|
|
4878
4878
|
},
|
|
4879
4879
|
"connections/elasticsearch": {
|
|
4880
4880
|
"files": [
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lowdefy/docs-content",
|
|
3
|
-
"version": "7.
|
|
3
|
+
"version": "7.4.0",
|
|
4
4
|
"license": "Apache-2.0",
|
|
5
5
|
"description": "Lowdefy documentation extracted as markdown for AI coding agents.",
|
|
6
6
|
"homepage": "https://lowdefy.com",
|
|
@@ -36,7 +36,7 @@
|
|
|
36
36
|
"scripts/*"
|
|
37
37
|
],
|
|
38
38
|
"dependencies": {
|
|
39
|
-
"@lowdefy/nunjucks": "7.
|
|
39
|
+
"@lowdefy/nunjucks": "7.4.0"
|
|
40
40
|
},
|
|
41
41
|
"publishConfig": {
|
|
42
42
|
"access": "public"
|