Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Using Force UI as a dependency in package.json -

```json
"dependencies": {
"@bsf/force-ui": "git+https://github.com/brainstormforce/force-ui#1.8.1"
"@bsf/force-ui": "git+https://github.com/brainstormforce/force-ui#1.8.2"
}
```

Expand All @@ -28,7 +28,7 @@ npm install
Or you can directly run the following command to install the package -

```bash
npm i -S @bsf/force-ui@git+https://github.com/brainstormforce/force-ui.git#1.8.1
npm i -S @bsf/force-ui@git+https://github.com/brainstormforce/force-ui.git#1.8.2
```

<br />
Expand Down
4 changes: 4 additions & 0 deletions changelog.txt
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
Version 1.8.2 - 8th September, 2026
- Fix: Installing the library as a git dependency on npm 9 failed with `Cannot read properties of null (reading 'edgesOut')` after Vitest 5 was released. Vite is now locked to `^6` through npm `overrides` so the dependency resolution can no longer drift to Vite 8 and pull in Vitest 5 peers.
- Improvement: Moved the build tooling from Vite 5 to Vite 6 and refreshed the lockfile. Published JavaScript and sourcemaps are byte-identical. `dist/tailwind.css` changes slightly due to the newer CSS minifier, and `dist/force-ui.d.ts` now imports the `JSX` namespace from `react` instead of `react/jsx-runtime` (same types, newer `@types/react`).

Version 1.8.1 - 11th August, 2026
- Improvement: Organism - Editor Input: Added optional `triggerRegex` prop that overrides the built-in mention-suggestion matcher, so consumers can allow the trigger without a leading blank space (e.g. directly after a double quote inside JSON string values). The custom regex must expose the same capture groups as the built-in matcher: 1 = leading boundary, 2 = replaceable string (trigger + query), 3 = query string used to filter options. When omitted, the existing trigger-based matcher is used unchanged.
- Fix: Atom - Select: In `multiple` mode the dropdown now stays open while selecting or deselecting options, closing only on Escape or outside click.
Expand Down
Loading
Loading