51a3cadd62
My scripted migration inserted the import behind a guard that silently did not fire:
`if 'defineMapElement' not in s.split('function')[0]` became false as soon as the
inserted CALL appeared before the first `function` keyword — so the files that most
needed the import were exactly the ones that did not get it. 11 of 16.
Every one of those elements would have thrown "defineMapElement is not defined" on
load. A bundler does not error on a free identifier; only loading does. studio caught it
in L64 via landing-preconditions, which imports each profile, and fixed it there
(37f75601) plus added an arm to check:element-bootstrap.
This repairs the same 11 on this branch so it is not a landmine if it lands after L64,
and it is byte-equivalent to studio's fix in effect. Verified by PARSING each entry and
resolving the identifier against its import bindings — 16 of 16 bound — rather than by
re-running the kind of regex that wrote the bug.
|
||
|---|---|---|
| .. | ||
| data | ||
| scripts | ||
| connectivity-list.meta.json | ||
| connectivity-list.vue | ||
| connectivity-map.meta.json | ||
| connectivity-map.vue | ||
| data-tables.meta.json | ||
| data-tables.vue | ||
| index.html | ||
| index.js | ||