@becklyn/deployment-protection 0.4.0 → 0.4.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 (11) hide show
  1. package/README.md +5 -3
  2. package/dist/cjs/storybook.d.ts +6 -2
  3. package/dist/cjs/storybook.d.ts.map +1 -1
  4. package/dist/cjs/storybook.js +6 -2
  5. package/dist/edge-bundles.json +7 -0
  6. package/dist/edge.mjs +974 -0
  7. package/dist/es/storybook.d.ts +6 -2
  8. package/dist/es/storybook.d.ts.map +1 -1
  9. package/dist/es/storybook.js +6 -2
  10. package/dist/storybook.mjs +974 -0
  11. package/package.json +17 -10
package/dist/es/storybook.d.ts CHANGED
@@ -1,10 +1,14 @@
1
1
  /**
2
2
  * Storybook deployment protection for Vercel.
3
3
  *
4
- * Built Storybooks are static sites, so protection runs as **Vercel Edge Middleware**
4
+ * Built Storybooks are static sites, so protection runs as **Vercel Routing Middleware**
5
5
  * (not Storybook config). Drop a `middleware.ts` next to the Vercel project root that
6
6
  * serves `storybook-static` and set the same env vars as the Next.js integration.
7
7
  *
8
+ * The published `./storybook` and `./edge` entry points resolve to self-contained ESM
9
+ * bundles so Vercel edge/nodejs middleware can load them without tracing multi-file
10
+ * package internals.
11
+ *
8
12
  * @example middleware.ts
9
13
  * ```ts
10
14
  * import { withStorybookDeploymentProtection } from "@becklyn/deployment-protection/storybook";
@@ -19,7 +23,7 @@
19
23
  * };
20
24
  * ```
21
25
  *
22
- * Optional `vercel.json` for a Storybook-only project:
26
+ * Optional `vercel.json` for a Storybook-only project (`framework` must be `null`):
23
27
  * ```json
24
28
  * {
25
29
  * "buildCommand": "npm run build-storybook",
package/dist/es/storybook.d.ts.map CHANGED
@@ -1 +1 @@
1
- {"version":3,"file":"storybook.d.ts","sourceRoot":"","sources":["../../src/storybook.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,EACH,qBAAqB,EACrB,4BAA4B,IAAI,iCAAiC,GACpE,MAAM,QAAQ,CAAC;AAChB,YAAY,EAAE,2BAA2B,EAAE,MAAM,SAAS,CAAC"}
1
+ {"version":3,"file":"storybook.d.ts","sourceRoot":"","sources":["../../src/storybook.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,OAAO,EACH,qBAAqB,EACrB,4BAA4B,IAAI,iCAAiC,GACpE,MAAM,QAAQ,CAAC;AAChB,YAAY,EAAE,2BAA2B,EAAE,MAAM,SAAS,CAAC"}
package/dist/es/storybook.js CHANGED
@@ -1,10 +1,14 @@
1
1
  /**
2
2
  * Storybook deployment protection for Vercel.
3
3
  *
4
- * Built Storybooks are static sites, so protection runs as **Vercel Edge Middleware**
4
+ * Built Storybooks are static sites, so protection runs as **Vercel Routing Middleware**
5
5
  * (not Storybook config). Drop a `middleware.ts` next to the Vercel project root that
6
6
  * serves `storybook-static` and set the same env vars as the Next.js integration.
7
7
  *
8
+ * The published `./storybook` and `./edge` entry points resolve to self-contained ESM
9
+ * bundles so Vercel edge/nodejs middleware can load them without tracing multi-file
10
+ * package internals.
11
+ *
8
12
  * @example middleware.ts
9
13
  * ```ts
10
14
  * import { withStorybookDeploymentProtection } from "@becklyn/deployment-protection/storybook";
@@ -19,7 +23,7 @@
19
23
  * };
20
24
  * ```
21
25
  *
22
- * Optional `vercel.json` for a Storybook-only project:
26
+ * Optional `vercel.json` for a Storybook-only project (`framework` must be `null`):
23
27
  * ```json
24
28
  * {
25
29
  * "buildCommand": "npm run build-storybook",