@omnitend/dashboard-for-laravel 0.42.1 → 0.43.0

package/dist/types/navigation.d.ts

@@ -34,6 +34,14 @@ export type Navigation = NavigationGroup[];
  * Shared by DXDashboard (which forwards it) and DXDashboardNavbar.
  */
 export type NavbarSearchAlign = "start" | "center";
+/**
+ * Colour scheme of the dashboard sidebar: `"light"` (the default: a white pane,
+ * tinted group headers, a green active item, Poppins) or `"dark"` (the navy
+ * rail dfl shipped before). Every colour comes from a `--dx-sidebar-*` custom
+ * property, so either can be rebranded in CSS. Shared by DXDashboard (which
+ * forwards it as `sidebarVariant`) and DXDashboardSidebar (`variant`).
+ */
+export type SidebarVariant = "light" | "dark";
 /**
  * What the navbar actions slot does below the `md` breakpoint: `"wrap"` moves
  * it to its own full-width row (the bar grows), `"hide"` removes it entirely

package/dist/utils/pageScrollLock.d.ts

@@ -0,0 +1,9 @@
+/**
+ * The class on <html> that stops the page scrolling behind DXDashboard's open
+ * phone menu (styled in theme.scss, below `sm` only).
+ */
+export declare const PAGE_SCROLL_LOCK_CLASS = "dx-dashboard-menu-open";
+/** Hold the page scroll lock for `owner`. Idempotent. */
+export declare const acquirePageScrollLock: (owner: object) => void;
+/** Release `owner`'s hold; the page unlocks once no owner holds it. Idempotent. */
+export declare const releasePageScrollLock: (owner: object) => void;

package/docs/public/api-reference.json

@@ -1,8 +1,8 @@
 {
-  "generated": "2026-10-05T05:06:30.259Z",
+  "generated": "2026-10-06T10:54:58.446Z",
   "package": {
     "name": "@omnitend/dashboard-for-laravel",
-    "version": "0.42.1"
+    "version": "0.43.0"
   },
   "components": {
     "base": [
@@ -907,7 +907,7 @@
         "name": "DModal",
         "category": "base",
         "filePath": "resources/js/components/base/DModal.vue",
-        "description": "",
+        "description": "Wrapper around bootstrap-vue-next's BModal. Two defaults differ from bvn's: `size=\"lg\"` (room for horizontal form labels on desktop) and `fullscreen=\"sm\"`: below 576px the modal covers the whole screen, with the header and footer pinned and the body scrolling between them (Bootstrap's `.modal-fullscreen-sm-down`). A `size=\"sm\"` modal (a short confirmation) keeps the centred small dialog on phones too. Pass `fullscreen` explicitly to override either way, e.g. `:fullscreen=\"false\"` to opt out.",
         "props": [],
         "events": [],
         "slots": [
@@ -1649,6 +1649,13 @@
             "default": "true",
             "description": "Only relevant when `collapsibleGroups` is on. `true` (default): only the\nactive-route group starts open and opening one closes the others\n(single-open accordion). `false`: all groups start open, toggled independently."
           },
+          {
+            "name": "sidebarVariant",
+            "type": "SidebarVariant",
+            "required": false,
+            "default": "'light'",
+            "description": "Sidebar colour scheme, forwarded to DXDashboardSidebar as `variant`:\n`'light'` (default: white pane, tinted group headers, green active item,\nPoppins) or `'dark'` (the navy rail). Colours come from the\n`--dx-sidebar-*` custom properties, so either can be rebranded in CSS."
+          },
           {
             "name": "storageKey",
             "type": "string",
@@ -1725,7 +1732,7 @@
             "type": "NavbarSearchAlign",
             "required": false,
             "default": "\"start\"",
-            "description": "Horizontal alignment of the search slot content within its region\n(`\"start\"` = flush left, `\"center\"` = centred). Applies at every size:\nthe region sits inline after the title from `md` up, and is its own\nfull-width row below."
+            "description": "Horizontal alignment of the search slot content within its region\n(`\"start\"` = flush left, `\"center\"` = centred). The region sits inline\nbetween the toggle/title and the user menu at every width."
           },
           {
             "name": "actionsOnMobile",
@@ -1740,6 +1747,20 @@
             "required": false,
             "default": "\"User menu\"",
             "description": "Accessible name for the user-menu trigger. Without one, a screen reader\nannounces the trigger as the avatar's initial (\"J\") rather than as a menu."
+          },
+          {
+            "name": "sidebarExpanded",
+            "type": "boolean",
+            "required": false,
+            "default": "undefined",
+            "description": "Whether the sidebar the toggle controls is showing, exposed as the\ntoggle's `aria-expanded`. Left unset, the toggle carries none.\nDXDashboard sets it."
+          },
+          {
+            "name": "sidebarId",
+            "type": "string",
+            "required": false,
+            "default": "\"\"",
+            "description": "`id` of the sidebar the toggle controls (its `aria-controls`)."
           }
         ],
         "events": [
@@ -1757,7 +1778,7 @@
           },
           {
             "name": "search",
-            "description": "Search input or component. Aligned per `searchAlign` within its region (inline in the bar from `md` up; its own full-width row below).",
+            "description": "Search input or component. Fills the middle of the bar at every width, aligned per `searchAlign`. The region is a size container named `dx-navbar-search`; a `<kbd>` hint inside it is hidden when it is narrower than 16rem.",
             "bindings": []
           },
           {
@@ -1879,13 +1900,37 @@
             "required": false,
             "default": "true",
             "description": "Only relevant when `collapsibleGroups` is on.\n`true` (default): only the active-route group starts open, and opening one\ngroup closes the others (single-open accordion).\n`false`: all groups start open and toggle independently."
+          },
+          {
+            "name": "variant",
+            "type": "SidebarVariant",
+            "required": false,
+            "default": "'light'",
+            "description": "Colour scheme: `'light'` (default) or `'dark'`. Colours come from the\n`--dx-sidebar-*` custom properties (see the theming guide), so either\nscheme can be rebranded in CSS."
+          },
+          {
+            "name": "phoneMenu",
+            "type": "boolean",
+            "required": false,
+            "default": "false",
+            "description": "Below `sm`, show the open sidebar as a full-screen menu over the page,\nwith a close button (which emits `close`), instead of a rail beside it;\nhidden there until opened. The owner must answer `close`, Escape and\n`navigate`: DXDashboard sets this and does. Off by default, so a\nstandalone sidebar keeps its rail on phones."
           }
         ],
         "events": [
+          {
+            "name": "close",
+            "description": "Emitted by the close button shown below `sm`, where the open sidebar covers the screen.",
+            "properties": []
+          },
           {
             "name": "toggle",
             "description": "Emitted to request toggling the sidebar's collapsed/expanded state.",
             "properties": []
+          },
+          {
+            "name": "navigate",
+            "description": "Emitted when a link anywhere in the sidebar is followed (a plain click,\nnot one that opens a new tab): the navigation, including links rendered\nthrough the `link` slot, and the `brand` and `footer` slots. DXDashboard\nuses it to close the full-screen menu on a phone.",
+            "properties": []
           }
         ],
         "slots": [
@@ -2806,7 +2851,7 @@
         "name": "DXNumberStepper",
         "category": "extended",
         "filePath": "resources/js/components/extended/DXNumberStepper.vue",
-        "description": "DXNumberStepper — a number input between a decrease and an increase button. `[ − ][ 12 ][ + ]` as one input group, for quantities that are usually nudged rather than typed (cases on an order line, covers on a booking). - The model is a number, or `null` when the input is empty (never `NaN`, never `\"\"`). Every step and every valid keystroke emits `update:modelValue`; debounce on the consumer's side if each change saves. - A step adds or subtracts `step` from the current value and clamps to `min`/`max`. It does not snap to a grid, so 1.05 + 0.1 is 1.15. The sum is rounded to the decimal places of the value and step, so 0.1 three times is 0.3, not 0.30000000000000004. From empty, a step goes to the in-range value nearest zero. - The button at a bound is disabled (decrease at `min`, increase at `max`). - Typing is free: the value is emitted as typed, even out of range, and is CLAMPED ON BLUR to `min`/`max` (emitting the clamped value). Half-typed input the browser cannot parse (\"-\", \"1e\") emits nothing until it parses. - ArrowUp/ArrowDown on the input go through the same step as the buttons (the browser's own spin-button stepping snaps to a grid; this does not). The native spin arrows are hidden. The buttons are `tabindex=\"-1\"`, so a list of steppers is one Tab stop each; keyboard users step with the arrows. - The buttons are square icon buttons at the input's height (never narrower than tall), soft `secondary` like other in-row actions, labelled \"Decrease\"/\"Increase\" plus the input's `aria-label` when it has one. `class` and `style` go on the group; every other attribute (`aria-label`, `name`, `id`, `placeholder`, `required`, `state`, listeners…) goes on the input. Styles live in theme.scss under `.dx-number-stepper`.",
+        "description": "DXNumberStepper — a number input between a decrease and an increase button. `[ − ][ 12 ][ + ]` as one input group, for quantities that are usually nudged rather than typed (cases on an order line, covers on a booking). - The model is a number, or `null` when the input is empty (never `NaN`, never `\"\"`). Every step and every valid keystroke emits `update:modelValue`; debounce on the consumer's side if each change saves. - Controlled: steps, the bound checks and blur all read `modelValue`. A parent may decline an emitted value (keep 2 when 2.5 is typed): blur then shows 2, + goes to 3, and a declined step is not left on screen. - A step adds or subtracts `step` from the current value and clamps to `min`/`max`. It does not snap to a grid, so 1.05 + 0.1 is 1.15. The sum is rounded to the decimal places of the value and step, so 0.1 three times is 0.3, not 0.30000000000000004. From empty, a step goes to the in-range value nearest zero. - The button at a bound is disabled (decrease at `min`, increase at `max`). - Typing is free: the value is emitted as typed, even out of range, and is CLAMPED ON BLUR to `min`/`max` (emitting the clamped value). Half-typed input the browser cannot parse (\"-\", \"1e\") emits nothing until it parses. - ArrowUp/ArrowDown on the input go through the same step as the buttons (the browser's own spin-button stepping snaps to a grid; this does not). The native spin arrows are hidden. The buttons are `tabindex=\"-1\"`, so a list of steppers is one Tab stop each; keyboard users step with the arrows. - The buttons are square icon buttons at the input's height (never narrower than tall), soft `secondary` like other in-row actions, labelled \"Decrease\"/\"Increase\" plus the input's `aria-label` when it has one. `class` and `style` go on the group; every other attribute (`aria-label`, `name`, `id`, `placeholder`, `required`, `state`, listeners…) goes on the input. Styles live in theme.scss under `.dx-number-stepper`.",
         "props": [
           {
             "name": "modelValue",
@@ -3157,6 +3202,35 @@
         ],
         "methods": []
       },
+      {
+        "name": "DXStackingTable",
+        "category": "extended",
+        "filePath": "resources/js/components/extended/DXStackingTable.vue",
+        "description": "",
+        "props": [
+          {
+            "name": "stackBelow",
+            "type": "number",
+            "required": false,
+            "default": "576",
+            "description": "Stack when the wrapper's content width is below this many px. 576 is\nBootstrap's `sm` breakpoint, but measured on the container."
+          }
+        ],
+        "events": [],
+        "slots": [
+          {
+            "name": "default",
+            "description": "The consumer's own `<table>`, as the wrapper's direct child.",
+            "bindings": [
+              {
+                "name": "stacked",
+                "title": "binding"
+              }
+            ]
+          }
+        ],
+        "methods": []
+      },
       {
         "name": "DXStatCard",
         "category": "extended",
@@ -4365,8 +4439,8 @@
     ]
   },
   "stats": {
-    "totalComponents": 88,
+    "totalComponents": 89,
     "baseComponents": 60,
-    "extendedComponents": 28
+    "extendedComponents": 29
   }
 }

package/docs/public/docs-map.md

@@ -1,7 +1,7 @@
 # Documentation Map
 
 > Auto-generated hierarchical overview of all documentation
-> Last updated: 2026-10-05T05:06:30.315Z
+> Last updated: 2026-10-06T10:54:58.500Z
 
 This file provides a complete map of all available documentation for AI agents and developers.
 
@@ -82,6 +82,7 @@ This file provides a complete map of all available documentation for AI agents a
 - [DXNumberStepper](/components/extended/DXNumberStepper): A number input between a decrease and an increase button, `[ − ][ 12 ][ + ]`,
 - [DXRepeater](/components/extended/DXRepeater): A repeatable sub-form (field array) primitive for nested, dynamic collections —
 - [DXSaveButton](/components/extended/DXSaveButton): A save button that confirms the save in place. While saving it shows
+- [DXStackingTable](/components/extended/DXStackingTable): A wrapper for a table you write yourself (an order's lines with price and
 - [DXStatCard](/components/extended/DXStatCard): A KPI / stat tile: a big formatted value with a title, optional subtitle, an
 - [DXSwitch](/components/extended/DXSwitch): A "filled box" toggle switch built on `DFormCheckbox`: a bordered box sized like
 - [DXTable](/components/extended/DXTable): A comprehensive data table component with built-in pagination, sorting, filtering, and CRUD operatio
@@ -104,4 +105,4 @@ This file provides a complete map of all available documentation for AI agents a
 
 ---
 
-**Total Pages**: 80
+**Total Pages**: 81

package/docs/public/llms.txt

@@ -2,7 +2,7 @@
 
 > Vue 3 dashboard components for Laravel with Bootstrap Vue Next
 >
-> A dual-package library (NPM + Composer) providing 78 Vue 3 components for building Laravel dashboards with Bootstrap Vue Next.
+> A dual-package library (NPM + Composer) providing 79 Vue 3 components for building Laravel dashboards with Bootstrap Vue Next.
 
 ## Installation
 
@@ -84,7 +84,7 @@ Lightweight type-safe wrappers around Bootstrap Vue Next components providing AP
 - [DToaster](/components/base/dtoaster): Bootstrap Vue Next Toaster wrapper
 - [DTooltip](/components/base/dtooltip): Bootstrap Vue Next Tooltip wrapper
 
-## Extended Components (18 components)
+## Extended Components (19 components)
 
 Custom dashboard components with advanced functionality beyond Bootstrap Vue Next.
 
@@ -101,6 +101,7 @@ Custom dashboard components with advanced functionality beyond Bootstrap Vue Nex
 - [DXNumberStepper](/components/extended/dxnumberstepper): Extended dashboard component
 - [DXRepeater](/components/extended/dxrepeater): Repeatable nested sub-form (field array) primitive
 - [DXSaveButton](/components/extended/dxsavebutton): Extended dashboard component
+- [DXStackingTable](/components/extended/dxstackingtable): Extended dashboard component
 - [DXStatCard](/components/extended/dxstatcard): Extended dashboard component
 - [DXSwitch](/components/extended/dxswitch): Extended dashboard component
 - [DXTable](/components/extended/dxtable): Data table with pagination, filtering, and sorting

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@omnitend/dashboard-for-laravel",
-  "version": "0.42.1",
+  "version": "0.43.0",
   "description": "Vue 3 dashboard components for Laravel with Bootstrap Vue Next",
   "type": "module",
   "main": "./dist/dashboard-for-laravel.umd.cjs",