@focusbc/bbs-lib 0.0.3 → 0.0.5

package/README.md

@@ -37,6 +37,18 @@ const context: MapContext = {
 
 const overlay = MapOverlay.initialize(document.getElementById('map-overlay')!, context)
 
+overlay.click().subscribe(({ shape, lat, lng }) => {
+  console.log('left click', { shape, lat, lng })
+})
+
+overlay.doubleClick().subscribe(({ shape, lat, lng }) => {
+  console.log('double click', { shape, lat, lng })
+})
+
+overlay.rightClick().subscribe(({ shape, lat, lng }) => {
+  console.log('right click', { shape, lat, lng })
+})
+
 // Later, when the event/site changes:
 overlay.setContext(newContext)
 ```
@@ -93,7 +105,7 @@ Open `http://localhost:5173`, select an event, then a site. The overlay calls `M
 
 ## Client demo
 
-The client-facing reference implementation lives in [`demo/`](demo/). It installs `@focusbc/bbs-lib` from **npm** (not the local `src/` or `dist/` in this repo) and bundles with esbuild. See [`demo/README.md`](demo/README.md).
+The client-facing reference implementation lives in [`demo/`](demo/). It is a static site (`index.html` + `main.js`) with no build step. See [`demo/README.md`](demo/README.md).
 
 From this directory:
 
@@ -107,6 +119,8 @@ Or from the repository root:
 yarn bbs-demo:serve
 ```
 
+To run the demo folder on its own, serve it statically — for example `npx --yes serve . -p 5174` from `demo/`.
+
 ---
 
 ## Releasing the library
@@ -148,7 +162,8 @@ When you run `yarn release:lib`, the script:
 2. Bumps `package.json` using `npm version <patch|minor|major> --no-git-tag-version`.
 3. Builds the package with `npm run build`.
 4. Publishes the package to `https://registry.npmjs.org/` with `npm publish --access public`.
-5. Re-encrypts the temporary `.npmrc` back into `.npmrc.enc`.
-6. Removes the plaintext `.npmrc` from disk.
+5. Uploads `dist/browser/bbs-lib.js` to Cloud Storage at `gs://bbs-lib-bucket/bbs-lib` (override with `BBS_LIB_BUCKET_URI` or `BBS_LIB_BUCKET`).
+6. Re-encrypts the temporary `.npmrc` back into `.npmrc.enc`.
+7. Removes the plaintext `.npmrc` from disk.
 
 If the release fails after the version bump, review `package.json` before retrying because the version may already have been changed locally.