webcomponents-bundle

Public GitHub Pages host for the built bundles of the private Facets-cloud/webcomponents monorepo.

Same idea as release-dashboard-bundle, but for the whole monorepo: the source stays private, the compiled custom-element bundles are published here so the control plane can load them by URL.

Hosted bundles

Served at https://facets-cloud.github.io/webcomponents-bundle/<file>:

Custom element	File
<blueprint-grouping>	blueprint-grouping-component.umd.js
<release-workflow>	release-workflow-component.umd.js
<environment-variables>	environment-variables-component.umd.js
<ops-center>	ops-center.js

(.es.js variants are also published for module usage.)

ops-center.js is the exception to everything below: it is not built from the monorepo. It is generated by a standalone build.py from a single prototype.html, and ships as one self-contained file with its screenshots inlined as data URIs — so it has no .es.js twin and no sibling asset directory. See "Updating" for the gap that leaves.

Use it

<script src="https://facets-cloud.github.io/webcomponents-bundle/blueprint-grouping-component.umd.js"></script>
<blueprint-grouping></blueprint-grouping>

Register in a control plane so it appears in the sidebar:

raptor create web-component blueprint-grouping \
  --remote-url https://facets-cloud.github.io/webcomponents-bundle/blueprint-grouping-component.umd.js \
  --enabled

Components use the viewer's session cookie and call /cc-ui/v1 relative to the host CP, so the same bundle works in any control plane.

Updating

Bundles are produced from the monorepo:

# in Facets-cloud/webcomponents
npm run build:all-components   # release-workflow + variables + blueprint
# copy dist/*.umd.js and dist/*.es.js here, commit, push

ops-center.js does not come from there. Its source is a standalone prototype.html plus build.py (which inlines the screenshots), currently living outside any repo:

python3 build.py     # rewrites ops-center.js from prototype.html + img/
# copy ops-center.js here, commit, push

Follow-up: wire the monorepo CI to push updated bundles here automatically on build.

Follow-up: ops-center has no source repo. Until prototype.html, build.py and img/ land somewhere shared, this bundle cannot be rebuilt or reviewed by anyone but its author, and a change request has nowhere to go.