create-foldkit-app 0.27.1 → 0.27.2
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/package.json
CHANGED
|
@@ -1,20 +1,7 @@
|
|
|
1
1
|
import { spawnSync } from 'node:child_process'
|
|
2
2
|
import { randomUUID } from 'node:crypto'
|
|
3
3
|
|
|
4
|
-
// NOTE: one id
|
|
5
|
-
// id, so the client bundle and the server bundle of a deployment agree on which
|
|
6
|
-
// deployment they are. `renderToString` stamps it on the prerendered pages and
|
|
7
|
-
// `Runtime.hydrate` compares it before adopting any DOM, so a page left over
|
|
8
|
-
// from an earlier deployment is refused and contained rather than reconciled
|
|
9
|
-
// against a client that no longer means the same thing by it.
|
|
10
|
-
//
|
|
11
|
-
// The id is published in the HTML every visitor receives. It identifies a
|
|
12
|
-
// deployment and is never a credential, so keep secrets out of it. Set
|
|
13
|
-
// FOLDKIT_BUILD_ID to name builds from a value the deployment already has, such
|
|
14
|
-
// as a commit or a release tag; without one, each build takes a fresh id.
|
|
15
|
-
// NOTE: `??` alone would take an empty FOLDKIT_BUILD_ID as a real value, and
|
|
16
|
-
// the plugin treats empty as absent, so the build would compile no id at all and
|
|
17
|
-
// fail later at the render. Empty is unset here too.
|
|
4
|
+
// NOTE: one nonempty id must reach every step in this build.
|
|
18
5
|
const supplied = process.env.FOLDKIT_BUILD_ID
|
|
19
6
|
const buildId =
|
|
20
7
|
supplied === undefined || supplied === '' ? randomUUID() : supplied
|
|
@@ -1,20 +1,7 @@
|
|
|
1
1
|
import { spawnSync } from 'node:child_process'
|
|
2
2
|
import { randomUUID } from 'node:crypto'
|
|
3
3
|
|
|
4
|
-
// NOTE: one id
|
|
5
|
-
// id, so the client bundle and the server bundle of a deployment agree on which
|
|
6
|
-
// deployment they are. `renderToString` stamps it on the rendered root and
|
|
7
|
-
// `Runtime.hydrate` compares it before adopting any DOM, so a page left over
|
|
8
|
-
// from an earlier deployment is refused and contained rather than reconciled
|
|
9
|
-
// against a client that no longer means the same thing by it.
|
|
10
|
-
//
|
|
11
|
-
// The id is published in the HTML every visitor receives. It identifies a
|
|
12
|
-
// deployment and is never a credential, so keep secrets out of it. Set
|
|
13
|
-
// FOLDKIT_BUILD_ID to name builds from a value the deployment already has, such
|
|
14
|
-
// as a commit or a release tag; without one, each build takes a fresh id.
|
|
15
|
-
// NOTE: `??` alone would take an empty FOLDKIT_BUILD_ID as a real value, and
|
|
16
|
-
// the plugin treats empty as absent, so the build would compile no id at all and
|
|
17
|
-
// fail later at the render. Empty is unset here too.
|
|
4
|
+
// NOTE: one nonempty id must reach every step in this build.
|
|
18
5
|
const supplied = process.env.FOLDKIT_BUILD_ID
|
|
19
6
|
const buildId =
|
|
20
7
|
supplied === undefined || supplied === '' ? randomUUID() : supplied
|