Skip to content

fix(widget): bump @deepgram/ui to ^0.1.1 for scoped tailwind preflight#48

Merged
lukeocodes merged 1 commit intomainfrom
fix/bump-deepgram-ui-to-0.1.1
May 6, 2026
Merged

fix(widget): bump @deepgram/ui to ^0.1.1 for scoped tailwind preflight#48
lukeocodes merged 1 commit intomainfrom
fix/bump-deepgram-ui-to-0.1.1

Conversation

@lukeocodes
Copy link
Copy Markdown
Member

Why

@deepgram/ui@0.1.1 (just published from deepgram/ui#27 + deepgram/ui#30) ships preflight scoped to [data-dg-agent] via tailwindcss-scoped-preflight. Until the widget bumps its dependency, the published UMD on cdn.deepgram.com/widgets/ still ships unscoped Tailwind preflight that bleeds into host pages.

Symptoms reported in deepgram/deepgram-docs#777: content width collapsed on every non-demo page on the docs site after the widget bundle finished loading. Same regression hits any customer embedding the widget on their own site.

What changed

  • packages/widget/package.json: @deepgram/ui ^0.1.0^0.1.1
  • bun.lock regenerated

Verification

Rebuilt the widget locally against @deepgram/ui@0.1.1:

before after
Unscoped @layer base{*,:after,…} rules in widget UMD many 0
:where([data-dg-agent], …) scoped rules 0 76
Total [data-dg-agent] occurrences 9 171

Bundle size: 384.30 KB → 387.53 KB (+3.23 KB) from the added scope selectors. Acceptable trade.

Expected after merge

  1. release-please opens chore(main): release agents-widget 0.1.4.
  2. Merging that PR bumps packages/widget/package.json to 0.1.4 and tags agents-widget-v0.1.4.
  3. The npm publish workflow pushes @deepgram/agents-widget@0.1.4 to npm.
  4. The CDN publish job uploads the new UMD bundle to:
    • https://cdn.deepgram.com/widgets/v0.1.4/widget.umd.js (immutable, 365-day TTL)
    • https://cdn.deepgram.com/widgets/latest/widget.umd.js (5-min TTL plus invalidation)
  5. Anyone loading either URL gets the scoped preflight.

Refs

@deepgram/ui@0.1.1 (deepgram/ui#27, deepgram/ui#30) ships preflight
scoped to [data-dg-agent] via tailwindcss-scoped-preflight. Bumping
the widget's @deepgram/ui dep brings the scoping into the published
widget UMD bundle and the CDN copy at cdn.deepgram.com/widgets/.

Verified locally by rebuilding the widget against 0.1.1:

  before (against 0.1.0): 0 :where([data-dg-agent]) rules in bundle
  after  (against 0.1.1): 76 :where([data-dg-agent]) rules in bundle

Bundle size grew 384.30 KB -> 387.53 KB (+3.23 KB) from the added
scope selectors.

Customer impact: any host page embedding the widget UMD no longer has
its box model, list styling, heading margins, or button appearance
overridden by Tailwind preflight. Widget components keep working
because the scoped preflight still applies inside [data-dg-agent].

Refs:
- deepgram/ui#27 (the fix itself)
- deepgram/ui#30 (release-please unpin to actually publish 0.1.1)
- deepgram/dx-stack#4 (gotchas + recipe doc)
@lukeocodes lukeocodes merged commit 0584d19 into main May 6, 2026
2 checks passed
@lukeocodes lukeocodes deleted the fix/bump-deepgram-ui-to-0.1.1 branch May 6, 2026 16:18
lukeocodes pushed a commit that referenced this pull request May 6, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.1.4](agents-widget-v0.1.3...agents-widget-v0.1.4)
(2026-05-06)


### Bug Fixes

* **widget:** bump @deepgram/ui to ^0.1.1 for scoped tailwind preflight
([#48](#48))
([0584d19](0584d19))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant