@justai/cim
v0.1.0
Published
City in Motion as data — the typed client for api.cityinmotion.nl, read at build time.
Readme
@justai/cim
City in Motion as data — the typed client for api.cityinmotion.nl, read at build time.
Why it is a package
It was cim-location/src/lib/city.ts until guess-back reached for the same stops() and the same
panoUrl(). Two consumers is the ecosystem's promotion trigger, and the tell is that you are about
to copy rather than to import.
cim-location still carries its own copy and moves onto this at its next touch. The lockfile
decides which persona a package reaches, and a fleet wave to land a refactor nobody is waiting for
costs more than it buys.
The two halves, and the line between them
| export | what it is for |
|---|---|
| stops() | the 38 standpoints — name, identity sentence, coordinates, and the pose an editor set |
| panoUrl(pose) | a still of that pose, through the graph-gated proxy |
panoUrl is the thumbnail surface, and naming it that matters now there is a second way to show
a panorama. A persona that fills the screen with one embeds Google's live StreetViewPanorama and
drives it with @justai/pano; this is for the picture in a list, in a card, in a choice.
It is read while the site is being built
Nothing here runs in a visitor's browser, and that was decided by the acceptance interview rather than by preference — item 37 ⛔ (it opens in airplane mode) and items 65/66 ⛔ (four Lighthouse numbers). A page that fetches its content on load fails the first outright and spends its budget on the second.
The honest cost, stated rather than discovered: content changes need a redeploy.
