Three fixes found by driving a real page, not by reading the code. Its autoloader works out where to fetch components from by finding the <script> whose src *ends with* "webawesome.loader.js". The cache-busting `?v=` defeated that match, so it fell back to the site root and every component 404'd - a page that merely looks unstyled, with nothing in the browser console and only 404s in the server log to say why. Web Awesome now lives at /chrome/wa-<version>/, which removes the query string and, because component filenames are stable across releases, also busts caches properly on an upgrade. There are regression tests for both halves. The brand ramp pointed at yellow but buttons came out brown: Web Awesome picks step 50 for a loud fill because that is the darkest point that still carries white text, and yellow-50 is #b45f04. The services have always used bright yellow with dark text, so the fill/on pair is now set explicitly rather than taken from the ramp. TemplateResponse's old (name, context) signature is gone in Starlette 1.7, and the error handler was returning its 404 page with an HTTP 200. Also adds the import map for Preact/hooks/htm to the shell. hooks.module.js carries a bare "preact" specifier internally, so the map is required rather than a convenience, and it belongs here once instead of in every service. strings_json() hands an island its translations with `<` escaped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| chrome | ||
| tests | ||
| .gitignore | ||
| LICENSE-webawesome.md | ||
| pyproject.toml | ||
| README.md | ||
| vendor-webawesome.sh | ||
chrome
The shared shell for the internal services: one page frame, one palette, one
set of components, one implementation of the handful of things every service
needs (config readers, proxy auth, /healthz, i18n, cache-busted assets).
It exists because the same stylesheet had been copied into four repositories
and had started to drift — along with theme.js, the asset() helper and
the error pages. A token change should be one commit here and a version bump
there, not four hand-edits with one forgotten.
What's in it
| Module | Replaces |
|---|---|
chrome.app.Chrome |
per-service app factory boilerplate, error pages, static mounts |
chrome.config |
three near-identical _bool/_int/_list env readers |
chrome.auth |
agent-bridge's Remote-User + proxy-key check |
chrome.health |
four copies of /healthz |
chrome.i18n |
homepage's pl/en machinery, which nothing else could reuse |
chrome.assets |
two different cache-busting strategies, one of them broken in containers |
templates/base.html |
four page shells |
static/tokens.css |
four copies of the design tokens |
UI components
Web Awesome (MIT, Fonticons) is vendored under
chrome/static/wa/. The autoloader registers each <wa-*> element the first
time it appears, so there is no per-component import list.
Components are styled inside a shadow root, which means a page rule cannot
reach into one. That is the point: "this input is the wrong width" stops being
a thing that can happen. Customise through --wa-* tokens and ::part().
Note that Combobox, Date Picker, File Input and the chart components are Web Awesome Pro, and are not vendored here. Use a native control or a different component.
Upgrading Web Awesome
./vendor-webawesome.sh 3.15.0 # then commit the diff
Plain curl and tar against the npm registry — no npm install, no
node_modules, no lockfile, nothing for CI or a Containerfile to run.
The script prunes type definitions and IDE metadata (~13M down to ~3.4M)
and keeps only the en and pl translations.
Using it
from fastapi import FastAPI
from chrome.app import Chrome
app = FastAPI()
ui = Chrome(
app,
service="marketplace",
version="0.2.0",
title="Skills Marketplace",
templates_dir=HERE / "templates",
static_dir=HERE / "static",
locales_dir=HERE / "locales",
)
@app.get("/")
def index(request: Request):
return ui.render(request, "index.html", things=[...])
Templates {% extends "base.html" %} and fill content. Service templates
and chrome's are both on the loader path, service first.
Depending on it
Pin a tag, not a branch:
dependencies = [
"chrome @ git+https://git.wierzbowa.cloud/michal/chrome@v0.1.0",
]
For the edit loop, install it editable alongside the service:
pip install -e ../chrome.
Theme convention
Pages use data-theme="light|dark|system" on <html>, which is what the
services have always used. Web Awesome drives light/dark from a wa-light /
wa-dark class instead; base.html and theme.js own that mapping, so no
service or stylesheet needs to know about it.