hyperframes 0.7.31 → 0.7.32
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/dist/cli.js +285 -192
- package/dist/hyperframe-runtime.js +10 -0
- package/dist/hyperframe.manifest.json +1 -1
- package/dist/hyperframe.runtime.iife.js +10 -0
- package/dist/studio/assets/{index-ClVRei_K.js → index-BRQ9g6Oo.js} +1 -1
- package/dist/studio/assets/{index-DeqMZHQ4.js → index-DsT9OH2w.js} +3 -3
- package/dist/studio/assets/{index-DM6n1UAe.js → index-XQiceQhf.js} +1 -1
- package/dist/studio/index.html +1 -1
- package/package.json +1 -1
|
@@ -204,6 +204,16 @@ https://www.w3ctech.com/topic/2226`));let c=n(...s);return c.postcssPlugin=e,c.p
|
|
|
204
204
|
? new Proxy(window, {
|
|
205
205
|
get: function(target, prop, receiver) {
|
|
206
206
|
if (prop === "__timelines") return __hfGetTimelineRegistry();
|
|
207
|
+
// Inside a sub-composition, __hyperframes is passed as a bare script
|
|
208
|
+
// param bound to the SCOPED variant (per-comp getVariables). But
|
|
209
|
+
// authors routinely write the documented window.__hyperframes.
|
|
210
|
+
// getVariables() form, which would otherwise fall through to the host
|
|
211
|
+
// page's base __hyperframes and return the WRONG (or empty) variables
|
|
212
|
+
// for this instance. Route it to the scoped variant too so both
|
|
213
|
+
// spellings resolve to this composition's own variables.
|
|
214
|
+
// (__hfScopedHyperframes is a hoisted var assigned below, before any
|
|
215
|
+
// sub-comp script -- the only code that reads this -- runs.)
|
|
216
|
+
if (prop === "__hyperframes") return __hfScopedHyperframes;
|
|
207
217
|
return Reflect.get(target, prop, target);
|
|
208
218
|
},
|
|
209
219
|
set: function(target, prop, value, receiver) {
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"version": "0.1.0",
|
|
3
3
|
"buildId": "dev",
|
|
4
|
-
"sha256": "
|
|
4
|
+
"sha256": "593865da2d8f8a10f0526e853488df292ec033075d7823294b1a5931fffb2b04",
|
|
5
5
|
"artifacts": {
|
|
6
6
|
"iife": "hyperframe.runtime.iife.js",
|
|
7
7
|
"esm": "hyperframe.runtime.mjs"
|
|
@@ -204,6 +204,16 @@ https://www.w3ctech.com/topic/2226`));let c=n(...s);return c.postcssPlugin=e,c.p
|
|
|
204
204
|
? new Proxy(window, {
|
|
205
205
|
get: function(target, prop, receiver) {
|
|
206
206
|
if (prop === "__timelines") return __hfGetTimelineRegistry();
|
|
207
|
+
// Inside a sub-composition, __hyperframes is passed as a bare script
|
|
208
|
+
// param bound to the SCOPED variant (per-comp getVariables). But
|
|
209
|
+
// authors routinely write the documented window.__hyperframes.
|
|
210
|
+
// getVariables() form, which would otherwise fall through to the host
|
|
211
|
+
// page's base __hyperframes and return the WRONG (or empty) variables
|
|
212
|
+
// for this instance. Route it to the scoped variant too so both
|
|
213
|
+
// spellings resolve to this composition's own variables.
|
|
214
|
+
// (__hfScopedHyperframes is a hoisted var assigned below, before any
|
|
215
|
+
// sub-comp script -- the only code that reads this -- runs.)
|
|
216
|
+
if (prop === "__hyperframes") return __hfScopedHyperframes;
|
|
207
217
|
return Reflect.get(target, prop, target);
|
|
208
218
|
},
|
|
209
219
|
set: function(target, prop, value, receiver) {
|