Add --bitgate-* theme tokens and a build-injected VERSION.

Widget styles now prefer --bitgate-* custom properties, falling back to the
deprecated --gov-* names and then the existing defaults so current pages and
overrides keep working. Browser bundles and ESM entry points expose VERSION
(and window.bitgate.version) from package.json. Document allowlist on the
widget policy preset list. Sync the lockfile so npm ci sees @bitgate/standalone.

Co-authored-by: thePR0M3TH3AN <[email protected]>
This commit is contained in:
Cursor AgentandthePR0M3TH3AN committed 2026-10-08 19:14:44 +00:00
1 parent 90d4290989
commit 9e6f6c659e
24 files changed
+369 -22

No files matched your search

+5
View File
@@ -87,6 +87,11 @@ allowlisted publishers are shown — the symmetric twin of a denylist, for
invite-only or curated surfaces). Every number in them is a starting point —
see the [integration guide](docs/integration-guide.md) to write your own.
The package version is exported as `VERSION` and, in browser bundles, as
`window.bitgate.version`. Both are injected from `package.json` at build time.
Widget theme tokens use `--bitgate-*` custom properties; the older `--gov-*`
names remain as fallbacks (see [`packages/widget/README.md`](packages/widget/README.md)).
## Quick start — JavaScript
```js