All files / src/constants index.ts

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
197x
36x
 
/**
 * Values fixed for every caller.
 *
 * @remarks
 * {@link cloudflareDefaults} is the conventional binding names from
 * `wrangler.json` plus conservative per-binding defaults — nothing that depends
 * on runtime state, which is what makes it a constant rather than part of the
 * engine that reads it.
 *
 * It is one half of a configuration surface. The kernel supplies
 * `systemDefaults` for whatever means the same thing on any runtime, and the
 * application joins them:
 *
 * ```ts
 * import { configure, systemDefaults } from '@bayudwiyansatria/core'
 * import { cloudflareDefaults } from '@bayudwiyansatria/cloudflare'
 *
 * configure(
 *   {
 *     ...systemDefaults,
 *     ...cloudflareDefaults,
 *     logging: { ...systemDefaults.logging, ...cloudflareDefaults.logging }
 *   },
 *   overrides
 * )
 * ```
 *
 * The halves are almost disjoint — the kernel owns `security`, this package owns
 * the binding-backed modules — so a flat spread carries all of those across.
 * `logging` is the one key both declare: the kernel sets the level, and
 * {@link cloudflareDefaults} narrows which context fields reach the line.
 * Spreading alone would drop one whole block for the other, and a bundler that
 * folds the two spreads into a single object literal reports the collision as a
 * `Duplicate key "logging"` warning on every `wrangler dev` and
 * `wrangler deploy` — so that one module is merged by hand.
 *
 * @module
 * @author Bayu Dwiyan Satria
 * @version 1.0.0
 * @since 1.0.0
 */
export { cloudflareDefaults } from '@/constants/Defaults'
export { events } from '@/constants/Events'