@thebase/ui 1.1.4 → 1.1.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,25 @@ All notable changes to this project are documented in this file.
4
4
 
5
5
  ## [Unreleased]
6
6
 
7
+ ## [v1.1.5] - 2026-10-17
8
+
9
+ ### Added
10
+ - Material outlined style is now shared by every input-like control: `Input`, `Textarea`, `NativeSelect`, `Combobox`, `DatePicker`, `Select` and `InputGroup` accept `label`, `supportingText`, `errorText`, `invalid` (and `leadingIcon`/`trailingIcon`/`maxLength` where they apply). The label rests inside and floats onto the border when focused or filled. Static `b-ui` adapters are unchanged. See the matching pages under `docs/components/`.
11
+ - `labelBackground` prop (any CSS colour) on every outlined control and on `Field`, to match the floating label's cut-out to the surrounding surface.
12
+ - `Field` accepts `label`, `description`, `error` and `invalid` and hands them to the control inside it.
13
+
14
+ ### Changed
15
+ - `Field` no longer renders its own label and error text; the control inside draws them. Use `FieldLabel` / `FieldError` for checkbox-style fields.
16
+ - Docs and examples: blocks (`field`, `textarea`, `date-picker`, `input-group`, `select`, `combobox`, `native-select`, `hover-card`, `login-03/04`, `signup-03/04`) use the `label` props; production pin examples now use `@1.1.5`; `qr-page` builds its VietQR/QR payload from CDN modules instead of vendored copies.
17
+ - `package.json` description no longer mentions Owl.
18
+
19
+ ## [v1.1.4] - 2026-10-14
20
+
21
+ Backfilled entry (1.1.4 shipped without release notes).
22
+
23
+ ### Changed
24
+ - Tabs, Toast and style-prop rollout; internal `baseui` class prefix renamed to `bu`; docs and memory synced.
25
+
7
26
  ## [v1.1.3] - 2026-10-13
8
27
 
9
28
  ### Added
package/README.md CHANGED
@@ -4,7 +4,7 @@ The Base UI is a CDN-installable UI kit built with Bootstrap 5 styling and Owl f
4
4
 
5
5
  Its strong points: **no build step** — every component runs straight from a CDN `<script>`/import map, nothing to compile; **modular component design** — each component is a self-contained unit you import or mark up individually, not a monolith; **vanilla JavaScript/TypeScript** — no framework lock-in, no JSX, no compiler-specific syntax to learn; and this combination makes it well suited to building **WYSIWYG website builders**, where components must mount, unmount, and re-render dynamically from user-driven markup or drag-and-drop edits rather than a fixed build-time component tree.
6
6
 
7
- Both APIs load straight from a CDN — jsDelivr or unpkg — no build step, no self-hosting required. The snippets below use the `@latest` tag for readability; pin an exact version instead (e.g. `@1.1.3`, or `@1` to take only non-breaking updates) for any production page, since `@latest` can change what your page loads the moment a new version ships. Pure Base usage:
7
+ Both APIs load straight from a CDN — jsDelivr or unpkg — no build step, no self-hosting required. The snippets below use the `@latest` tag for readability; pin an exact version instead (e.g. `@1.1.5`, or `@1` to take only non-breaking updates) for any production page, since `@latest` can change what your page loads the moment a new version ships. Pure Base usage:
8
8
 
9
9
  ```html
10
10
  <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@thebase/ui@latest/dist/baseui.min.css">
@@ -81,13 +81,17 @@ npx create-baseui-app pwa . --config baseui.pwa.config.js
81
81
 
82
82
  See [Usage Guide §5b](docs/usage-guide.md) and the [PWA component](docs/components/pwa.md). The examples site itself is an installable PWA (`examples/pwa/`).
83
83
 
84
+ ## Outlined fields
85
+
86
+ New in 1.1.5: `Input`, `Textarea`, `NativeSelect`, `Combobox`, `DatePicker`, `Select` and `InputGroup` share one Material-style outlined look (`label`, `supportingText`, `errorText`, `invalid`), and `Field` passes its `label`/`description`/`error` to the control inside. See [Field](docs/components/field.md) and [Input](docs/components/input.md).
87
+
84
88
  ## ApiDoc
85
89
 
86
90
  New in 1.1.3: `ApiDoc` (`b-ui="apidoc"`) renders an OpenAPI 3 JSON file as browsable API docs — grouped sidebar, parameters, request bodies, responses, a Try It panel with code samples in 17 languages, and an Authorize dialog. See [ApiDoc](docs/components/apidoc.md), the `apidoc-01` block, and the live demo in [`examples/apidoc/`](examples/apidoc/).
87
91
 
88
92
  ## Release notes
89
93
 
90
- See [CHANGELOG.md](CHANGELOG.md) for the full version history. Current version: **1.1.3**.
94
+ See [CHANGELOG.md](CHANGELOG.md) for the full version history. Current version: **1.1.5**.
91
95
 
92
96
  ## Versioning policy
93
97
 
@@ -106,7 +110,7 @@ What each release type means:
106
110
 
107
111
  Anything prefixed `_`, undocumented internals, and the `docs/`/`examples/` sources are not part of the public API. Neither are the source-level authoring helpers described in [Component Authoring](docs/component-authoring.md) (`optional()`, `slotProps`, the `open-state.js` hooks, `bindBootstrapOverlay()`): they aren't exported from the package and may change in any release. Deprecated APIs keep working until the next major and are flagged in the CHANGELOG first.
108
112
 
109
- Pinning: use an exact version (`@1.1.3`) when you need byte-identical output, or the major range (`@1` on jsDelivr/unpkg, `^1.0.0` in npm) to receive fixes and features without breaking changes. Avoid `@latest` in production — it will move to the next major.
113
+ Pinning: use an exact version (`@1.1.5`) when you need byte-identical output, or the major range (`@1` on jsDelivr/unpkg, `^1.0.0` in npm) to receive fixes and features without breaking changes. Avoid `@latest` in production — it will move to the next major.
110
114
 
111
115
  ## Project Documents
112
116