@gitlab/ui 96.3.0 → 97.0.0

package/src/vendor/bootstrap-vue/src/components/form-checkbox/README.md

@@ -361,8 +361,8 @@ This will inform users of assistive technologies that the checkboxes are related
 browser keyboard navigation.
 
 Whenever using multiple checkboxes, it is recommended that the checkboxes be placed in a
-[`<b-form-group>`](/docs/components/form-group) component to associate a label with the entire group
-of checkboxes. See examples above.
+[`<gl-form-group>`](?path=/docs/base-form-form-group--docs) component to associate a label with the
+entire group of checkboxes. See examples above.
 
 ## Button style checkboxes
 
@@ -376,8 +376,8 @@ are in the _checked_ state.
 A single checkbox can be rendered with a button appearance by setting the prop `button` to `true`
 
 Change the button variant by setting the `button-variant` prop to one of the standard Bootstrap
-button variants (see [`<b-button>`](/docs/components/button) for supported variants). The default
-variant is `secondary`.
+button variants (see [`<gl-button>`](?path=/docs/base-button--docs) for supported variants). The
+default variant is `secondary`.
 
 ```html
 <template>
@@ -411,8 +411,8 @@ The `inline` prop has no effect on individual button-style checkboxes.
 
 Render groups of checkboxes with the look of a button-group by setting the prop `buttons` on
 `<b-form-checkbox-group>`. Change the button variant by setting the `button-variant` prop to one of
-the standard Bootstrap button variants (see [`<b-button>`](/docs/components/button) for supported
-variants). The default `button-variant` is `secondary`.
+the standard Bootstrap button variants (see [`<gl-button>`](?path=/docs/base-button--docs) for
+supported variants). The default `button-variant` is `secondary`.
 
 ```html
 <template>

package/src/vendor/bootstrap-vue/src/components/form-group/README.md

@@ -84,7 +84,8 @@ occupy in the row via the `content-cols` and `content-cols-{breakpoint}` props.
 When using both, the `label-cols` and `content-cols` props, make sure that the total amount of
 columns doesn't exceed `12`.
 
-See the [Layout and Grid System](/docs/components/layout#how-it-works) docs for further information.
+See the [Layout and Grid System](?path=/docs/base-form-form-group--docs#how-it-works) docs for
+further information.
 
 | Prop              | Description                                                                           |
 | ----------------- | ------------------------------------------------------------------------------------- |
@@ -165,7 +166,7 @@ Alignment has no effect if the `label-sr-only` prop is set.
 
 Optional descriptive text which is always shown with the `.text-muted` class by setting the
 `description` prop or using the named slot `description`. The description text is rendered using the
-[`<b-form-text>`](/docs/components/form#helper-components) form sub-component.
+[`<b-form-text>`](?path=/docs/base-form-form--docs#helper-components) form sub-component.
 
 ## Nested form groups
 
@@ -281,7 +282,8 @@ Show optional invalid state feedback text to provide textual state feedback (htm
 setting the prop `invalid-feedback` or using the named slot `invalid-feedback`.
 
 Invalid feedback is rendered using the
-[`<b-form-invalid-feedback>`](/docs/components/form#helper-components) form sub-component.
+[`<b-form-invalid-feedback>`](?path=/docs/base-form-form--docs#helper-components) form
+sub-component.
 
 ### Valid feedback
 
@@ -289,7 +291,7 @@ Show optional valid state feedback text to provide textual state feedback (html
 setting the prop `valid-feedback` or using the named slot `valid-feedback`.
 
 Valid feedback is rendered using the
-[`<b-form-valid-feedback>`](/docs/components/form#helper-components) form sub-component.
+[`<b-form-valid-feedback>`](?path=/docs/base-form-form--docs#helper-components) form sub-component.
 
 ### Feedback style
 

package/src/vendor/bootstrap-vue/src/components/form-input/README.md

@@ -304,8 +304,8 @@ invalid), `true` (for valid), or `null` (no validation state).
 <!-- b-form-input-states-feedback.vue -->
 ```
 
-> **Tip:** Use the [`<b-form-group>`](/docs/components/form-group) component to automatically
-> generate markup similar to above.
+> **Tip:** Use the [`<gl-form-group>`](?path=/docs/base-form-form-group--docs) component to
+> automatically generate markup similar to above.
 
 ### Conveying contextual state to assistive technologies and colorblind users
 
@@ -463,8 +463,8 @@ chosen, or new values to be entered.
 ```
 
 BootstrapVue provides the form helper component
-[`<b-form-datalist>`](/docs/components/form/#datalist-helper) for quickly creating a `<datalist>`
-from an array of options.
+[`<b-form-datalist>`](?path=/docs/base-form-form--docs#datalist-helper) for quickly creating a
+`<datalist>` from an array of options.
 
 **Notes:**
 

package/src/vendor/bootstrap-vue/src/components/form-radio/README.md

@@ -345,7 +345,7 @@ BootstrapVue includes custom SCSS/CSS that adds support for sizing the custom ra
 
 Render radios with the look of buttons by setting the prop `buttons` to `true` on
 `<b-form-radio-group>`. Set the button variant by setting the `button-variant` prop to one of the
-standard Bootstrap button variants (see [`<b-button>`](/docs/components/button) for supported
+standard Bootstrap button variants (see [`<gl-button>`](?path=/docs/base-button--docs) for supported
 variants). The default `button-variant` is `secondary`.
 
 The `buttons` prop has precedence over `plain`, and `button-variant` has no effect if `buttons` is

package/src/vendor/bootstrap-vue/src/components/index.d.ts

@@ -24,7 +24,6 @@ export * from './modal'
 export * from './nav'
 export * from './navbar'
 export * from './popover'
-export * from './progress'
 export * from './table'
 export * from './tabs'
 export * from './toast'

package/src/vendor/bootstrap-vue/src/components/input-group/README.md

@@ -117,15 +117,10 @@ when you want to use on of [BootstrapVue's icons](/docs/icons).
 
 The following are the form controls supported as the input-group's _main_ input element:
 
-- [`<b-form-input>`](/docs/components/form-input)
-- [`<b-form-textarea>`](/docs/components/form-textarea)
-- [`<b-form-select>`](/docs/components/form-select)
-- [`<b-form-file>`](/docs/components/form-file)
-- [`<b-form-rating>`](/docs/components/form-rating)
-- [`<b-form-tags>`](/docs/components/form-tags)
-- [`<b-form-spinbutton>`](/docs/components/form-spinbutton)
-- [`<b-form-datepicker>`](/docs/components/form-datepicker)
-- [`<b-form-timepicker>`](/docs/components/form-timepicker)
+- [form-input](?path=/docs/base-form-form-input--docs)
+- [form-textarea](?path=/docs/base-form-form-textarea--docs)
+- [form-select](?path=/docs/base-form-form-select--docs)
+- [form-date](?path=/docs/base-form-form-date--docs)
 
 **Notes:**
 

package/src/vendor/bootstrap-vue/src/components/layout/README.md

@@ -147,13 +147,13 @@ You can remove the margin from `<b-row>` and padding from `<b-col>` by setting t
 on `<b-row>`.
 
 Or, for compact margins (smaller gutters between columns), use the `<b-form-row>` component, which
-is typically used when laying out [forms](/docs/components/form).
+is typically used when laying out [forms](?path=/docs/base-form-form--docs).
 
 ## Columns `<b-col>`
 
 `<b-col>` Must be placed inside a `<b-row>` component, or an element (such as a `<div>`) that has
-the class `row` applied to it, or - in the case of [forms](/docs/components/form) - inside a
-`<b-form-row>` component (to obtain columns with more compact margins).
+the class `row` applied to it, or - in the case of [forms](?path=/docs/base-form-form--docs) -
+inside a `<b-form-row>` component (to obtain columns with more compact margins).
 
 ## Grid options
 

package/src/vendor/bootstrap-vue/src/components/link/README.md

@@ -19,7 +19,7 @@ By specifying a value in the `href` prop, a standard link (`<a>`) element will b
 generate a `<router-link>` instead, specify the route location via the `to` prop.
 
 Router links support various additional props. Refer to the
-[Router support](/docs/reference/router-links) reference section for details.
+[Router support](?path=/docs/base-link--docs#router-link-support) reference section for details.
 
 If your app is running under [Nuxt.js](https://nuxtjs.org), the
 [`<nuxt-link>`](https://nuxtjs.org/api/components-nuxt-link) component will be used instead of

package/src/vendor/bootstrap-vue/src/components/modal/README.md

@@ -898,8 +898,8 @@ emitted.
 
 **Note:** The animation effect of this component is dependent on the `prefers-reduced-motion` media
 query. See the
-[reduced motion section of our accessibility documentation](/docs/reference/accessibility) for
-additional details.
+[reduced motion section of our accessibility documentation](?path=/docs/base-tooltip--docs#accessibility)
+for additional details.
 
 ### Modal ARIA attributes
 

package/src/vendor/bootstrap-vue/src/components/nav/README.md

@@ -277,18 +277,18 @@ Use the `<b-nav-form>` child component to place an _inline_ form into the nav:
 <!-- b-nav-form.vue -->
 ```
 
-Refer to the [`<b-form>` inline](/docs/components/form#inline-form) documentation for additional
-details on placing form controls.
+Refer to the [`<gl-form>` inline](?path=/docs/base-form-form--docs#inline-formm) documentation for
+additional details on placing form controls.
 
 ## Tabbed local content support
 
-See the [`<b-tabs>`](/docs/components/tabs) component for creating tabbable panes of local content
-(not suited for navigation).
+See the [`<gl-tabs>`](?path=/docs/base-tabs--docs) component for creating tabbable panes of local
+content (not suited for navigation).
 
 ## Card integration
 
-Use a `<b-nav>` in a [`<b-card>`](/docs/components/card) header, by enabling the `card-header` prop
-on `<b-nav>` and setting either the `pills` or `tabs` props:
+Use a `<b-nav>` in a [`<gl-card>`](?path=/docs/base-card--docs) header, by enabling the
+`card-header` prop on `<b-nav>` and setting either the `pills` or `tabs` props:
 
 **Tabs style:**
 
@@ -453,9 +453,10 @@ generated.
 
 Note that navigation bars, even if visually styled as tabs, should **not** be given
 `role="tablist"`, `role="tab"` or `role="tabpanel"` attributes. These are only appropriate for
-[tabbed interfaces](/docs/components/tabs) that do not change the URL or `$route`, as described in
-the [WAI ARIA Authoring Practices](https://www.w3.org/TR/wai-aria-practices/#tabpanel). See
-[`<b-tabs>`](/docs/components/tabs) for dynamic tabbed interfaces that are compliant with WAI ARIA.
+[tabbed interfaces](?path=/docs/base-tabs--docs) that do not change the URL or `$route`, as
+described in the [WAI ARIA Authoring Practices](https://www.w3.org/TR/wai-aria-practices/#tabpanel).
+See [`<gl-tabs>`](?path=/docs/base-tabs--docs) for dynamic tabbed interfaces that are compliant with
+WAI ARIA.
 
 Tabbed interfaces should avoid using dropdown menus, as this causes both usability and accessibility
 issues:
@@ -468,13 +469,11 @@ issues:
 
 ## See also
 
-- [`<b-tabs>`](/docs/components/tabs) to create tabbable panes of local content, even via dropdown
+- [tabs](?path=/docs/base-tabs--docs) to create tabbable panes of local content, even via dropdown
   menus.
-- [`<b-navbar>`](/docs/components/navbar) a wrapper that positions branding, navigation, and other
-  elements in a concise header.
 - [`<b-dropdown>`](/docs/components/dropdown) for sub-components that you can place inside
   `<b-nav-item-dropdown>`
-- [Router Link Support reference](/docs/reference/router-links) for information about router-link
-  specific props available on `<b-nav-item>`
+- [Router Link Support reference](?path=/docs/base-link--docs#router-link-support) for information
+  about router-link specific props available on `<b-nav-item>`
 
 <!-- Component reference added automatically from component package.json -->

package/src/vendor/bootstrap-vue/src/components/navbar/README.md

@@ -279,7 +279,7 @@ like `<b-navbar-brand>`, they'll automatically be aligned to the far right. Reve
 will reverse the placement of the toggler.
 
 See the first example on this page for reference, and also refer to
-[`<b-collapse>`](/docs/components/collapse) for details on the collapse component.
+[`<gl-collapse>`](?path=/docs/base-collapse--docs) for details on the collapse component.
 
 Internally, `<b-navbar-toggle>` uses the [`v-b-toggle` directive](/docs/directives/toggle).
 
@@ -322,12 +322,11 @@ Navbars are hidden by default when printing. Force them to be printed by setting
 
 ## See also
 
-- [`<b-collapse>` component](/docs/components/collapse)
+- [collapse](?path=/docs/base-collapse--docs)
 - [`v-b-toggle` directive](/docs/directives/toggle)
-- [`<b-nav>` documentation](/docs/components/nav) for additional components and sub-component
-  aliases
+- [nav](?path=/docs/base-nav--docs) for additional components and sub-component aliases
 
-Refer to the [Router support](/docs/reference/router-links) reference page for router-link specific
-props.
+Refer to the [Router support](?path=/docs/base-link--docs#router-link-support) reference page for
+router-link specific props.
 
 <!-- Component reference added automatically from component package.json -->

package/src/vendor/bootstrap-vue/src/components/popover/README.md

@@ -61,7 +61,7 @@ Twelve options are available for positioning: `top`, `topleft`, `topright`, `rig
 `rightbottom`, `bottom`, `bottomleft`, `bottomright`, `left`, `lefttop`, and `leftbottom` aligned.
 Positioning is relative to the trigger element.
 
-<div class="bd-example bd-example-popover-static">
+<section class="bd-example bd-example-popover-static">
   <div class="popover b-popover bs-popover-top bs-popover-top-docs">
     <div class="arrow" style="left: calc(50% - 8px)"></div>
     <h3 class="popover-header">Popover top</h3>
@@ -163,7 +163,7 @@ Positioning is relative to the trigger element.
   </div>
 
   <div class="clearfix"></div>
-</div>
+</section>
 
 ## Triggers
 
@@ -887,8 +887,8 @@ interacting with it (keeping focus inside the popover until it is closed by the
 
 **Note:** The animation effect of this component is dependent on the `prefers-reduced-motion` media
 query. See the
-[reduced motion section of our accessibility documentation](/docs/reference/accessibility) for
-additional details.
+[reduced motion section of our accessibility documentation](?path=/docs/base-tooltip--docs#accessibility)
+for additional details.
 
 ### Making popovers work for keyboard and assistive technology users
 

package/src/vendor/bootstrap-vue/src/components/table/README.md

@@ -2168,7 +2168,7 @@ Setting the prop `filter` to null or an empty string will clear local items filt
 ### Debouncing filter criteria changes
 
 <span class="badge badge-warning small">deprecated in v2.1.0</span> Use the `debounce` feature of
-[`<b-form-input>`](/docs/components/form-input#debounce-support) instead.
+[form-input](?path=/docs/base-form-form-input--docst#debounce-support) instead.
 
 If you have a text input tied to the `filter` prop of `<b-table>`, the filtering process will occur
 for each character typed by the user. With large items datasets, this process can take a while and
@@ -2198,7 +2198,7 @@ at a time by setting the `per-page` prop to the maximum number of rows you would
 use the `current-page` prop to specify which page to display (starting from page `1`). If you set
 `current-page` to a value larger than the computed number of pages, then no rows will be shown.
 
-You can use the [`<b-pagination>`](/docs/components/pagination) component in conjunction with
+You can use the [`<gl-pagination>`](?path=/docs/base-pagination--docs) component in conjunction with
 `<b-table>` for providing control over pagination.
 
 Setting `per-page` to `0` (default) will disable the local items pagination feature.
@@ -2415,9 +2415,9 @@ of records.
   respective `no-provider-*` prop set to `true`).
 - The `no-local-sorting` prop has no effect when `items` is a provider function.
 - When using provider filtering, you may find that setting the
-  [`debounce` prop on `<b-form-input>`](/docs/components/form-input#debounce-support) to a value
-  greater than `100` ms will help minimize the number of calls to your back end API as the user
-  types in the criteria.
+  [`debounce` prop on `<gl-form-input>`](?path=/docs/base-form-form-input--docs#debounce-support) to
+  a value greater than `100` ms will help minimize the number of calls to your back end API as the
+  user types in the criteria.
 
 ### Force refreshing of table data
 

package/src/vendor/bootstrap-vue/src/components/tabs/README.md

@@ -4,7 +4,7 @@
 > cards internally, and provides full keyboard navigation control of the tabs.
 
 For navigation based tabs (i.e. tabs that would change the URL), use the
-[`<b-nav>`](/docs/components/nav) component instead.
+[nav](?path=/docs/base-nav--docs) component instead.
 
 ## Basic usage
 
@@ -91,7 +91,7 @@ When `<b-tabs>` is in `card` mode, each `<b-tab>` sub-component will automatical
 **Note:** Setting the `no-body` prop on `<b-tab>` will have no affect when `<b-tabs>` is not in
 `card` mode (as the `card-body` class is only set when in `card` mode).
 
-Refer to the [Cards documentation](/docs/components/card) for more details on card components.
+Refer to the [Cards documentation](?path=/docs/base-card--docs) for more details on card components.
 
 ## Pills variant
 

package/src/vendor/bootstrap-vue/src/components/toast/README.md

@@ -22,7 +22,7 @@ under the toast.
 
 ```html
 <template>
-  <div class="p-3 bg-secondary progress-bar-striped" style="min-height: 170px;">
+  <div class="p-3 bg-secondary" style="min-height: 170px;">
     <b-button class="mb-2" variant="primary" @click="$bvToast.show('example-toast')">
       Show toast
     </b-button>
@@ -36,8 +36,8 @@ under the toast.
 ```
 
 **Note:** we are using the `static` prop in the above example to render the toast in-place in the
-document, rather than transporting it to a `<b-toaster>` target container. And we have added classes
-`bg-secondary` and `progress-bar-striped` to the outer `<div>` for illustrative purposes of toast
+document, rather than transporting it to a `<b-toaster>` target container. And we have added class
+`bg-secondary` to the outer `<div>` for illustrative purposes of toast
 transparency only.
 
 ### Toast features and notes
@@ -535,7 +535,7 @@ for generating more complex toast content:
 In some cases you may need just a simple alert style message (i.e. cookie usage notifications,
 etc.). In these cases it is usually better to use an fixed position alert instead of a toast, by
 applying a few Bootstrap [utility classes](/docs/reference/utility-classes) and a small bit of
-custom styling on a [`<b-alert>`](/docs/components/alert) component:
+custom styling on a [`<gl-alert>`](?path=/docs/base-alert--docs) component:
 
 ```html
 <template>
@@ -615,7 +615,7 @@ that can impact both people with and without disabilities. The following list, w
 provides general guidelines when using toasts.
 
 - If the information needed is important for the process, e.g. for a list of errors in a form, then
-  use the [`<b-alert>`](/docs/components/alert) component instead of `<b-toast>`.
+  use the [`<gl-alert>`](?path=/docs/base-alert--docs) component instead of `<b-toast>`.
 - `<b-toast>`, by default, sets the attributes `role` to `'alert'` and `aria-live` to `'assertive'`.
   If it's an important message like an error, this default setting is appropriate, otherwise set the
   prop `is-status` to `true` which will change the attributes `role` to `'status'` and `aria-live`

package/src/vendor/bootstrap-vue/src/components/tooltip/README.md

@@ -64,7 +64,7 @@ Twelve options are available for positioning: `top`, `topleft`, `topright`, `rig
 `rightbottom`, `bottom`, `bottomleft`, `bottomright`, `left`, `lefttop`, and `leftbottom` aligned.
 The default position is `top`. Positioning is relative to the trigger element.
 
-<div class="bd-example bd-example-tooltip-static">
+<section class="bd-example bd-example-tooltip-static">
   <div class="tooltip b-tooltip bs-tooltip-top bs-tooltip-top-docs" role="tooltip">
     <div class="arrow" style="left: calc(50% - 6px)"></div>
     <div class="tooltip-inner">Tooltip on the top</div>
@@ -113,7 +113,7 @@ The default position is `top`. Positioning is relative to the trigger element.
     <div class="arrow" style="top: 0px"></div>
     <div class="tooltip-inner">Tooltip on the leftbottom</div>
   </div>
-</div>
+</section>
 
 Refer to the [Tooltip directive](/docs/directives/tooltip/#positioning) documentation for live
 examples of positioning.
@@ -553,7 +553,7 @@ with the auto generated ID of the tooltip.
 
 **Note:** The animation effect of this component is dependent on the `prefers-reduced-motion` media
 query. See the
-[reduced motion section of our accessibility documentation](/docs/reference/accessibility) for
-additional details.
+[reduced motion section of our accessibility documentation](?path=/docs/base-tooltip--docs#accessibility)
+for additional details.
 
 <!-- Component reference added automatically from component package.json -->

package/src/vendor/bootstrap-vue/src/constants/components.js

@@ -44,8 +44,6 @@ export const NAME_NAVBAR_BRAND = 'BNavbarBrand'
 export const NAME_NAV_ITEM = 'BNavItem'
 export const NAME_NAV_ITEM_DROPDOWN = 'BNavItemDropdown'
 export const NAME_POPOVER = 'BPopover'
-export const NAME_PROGRESS = 'BProgress'
-export const NAME_PROGRESS_BAR = 'BProgressBar'
 export const NAME_TAB = 'BTab'
 export const NAME_TABLE = 'BTable'
 export const NAME_TABLE_CELL = 'BTableCell'

package/src/vendor/bootstrap-vue/src/directives/toggle/README.md

@@ -1,12 +1,13 @@
 # Toggle
 
-> `v-b-toggle` is a light-weight directive for toggling the visibility of collapses,
-> and includes automated [WAI-ARIA accessibility](/docs/reference/accessibility) attribute handling.
+> `v-b-toggle` is a light-weight directive for toggling the visibility of collapses, and includes
+> automated [WAI-ARIA accessibility](?path=/docs/base-tooltip--docs#accessibility) attribute
+> handling.
 
 ## Overview
 
 The `v-b-toggle` directive can be used on interactive elements, such as buttons and to toggle the
-visibility state of the [`<b-collapse>`](/docs/components/collapse) component.
+visibility state of the [`<gl-collapse>`](?path=/docs/base-collapse--docs) component.
 
 Besides toggling the visibility of the target component, the directive automatically updates ARIA
 accessibility attributes on the element it is applied to so that they reflect the visibility state
@@ -141,6 +142,4 @@ via `v-model`, other controls with `v-b-toggle` directive, or CSS visibility).
 
 ## See also
 
-- [`<b-collapse>`](/docs/components/collapse) Collapsible content with accordion support
-- [`<b-navbar-toggle>`](/docs/components/navbar#b-navbar-toggle-and-b-collapse-is-nav) Navbar
-  hamburger toggle button (based on `v-b-toggle` directive)
+- [collapse](?path=/docs/base-collapse--docs) Collapsible content with accordion support

package/src/vendor/bootstrap-vue/src/directives/tooltip/README.md

@@ -515,7 +515,7 @@ disabled.
 
 ## See also
 
-- [`<b-tooltip>` component](/docs/components/tooltip)
-- [`<b-popover>` component](/docs/components/popover)
+- [tooltip](?path=/docs/base-tooltip--docs)
+- [popover](?path=/docs/base-popover--docs)
 
 <!-- Directive reference section auto generated from directive package.json -->

package/src/vendor/bootstrap-vue/src/index.js

@@ -135,10 +135,6 @@ export { BNavbarBrand } from './components/navbar/navbar-brand'
 // export * from './components/popover'
 export { BPopover } from './components/popover/popover'
 
-// export * from './components/progress'
-export { BProgress } from './components/progress/progress'
-export { BProgressBar } from './components/progress/progress-bar'
-
 // export * from './components/table'
 export { BTable } from './components/table/table'
 export { BTableLite } from './components/table/table-lite'

package/dist/vendor/bootstrap-vue/src/components/progress/index.js

@@ -1,2 +0,0 @@
-export { BProgress } from './progress';
-export { BProgressBar } from './progress-bar';

package/dist/vendor/bootstrap-vue/src/components/progress/progress-bar.js

@@ -1,128 +0,0 @@
-import { extend } from '../../vue';
-import { NAME_PROGRESS_BAR } from '../../constants/components';
-import { PROP_TYPE_BOOLEAN, PROP_TYPE_STRING, PROP_TYPE_NUMBER_STRING } from '../../constants/props';
-import { htmlOrText } from '../../utils/html';
-import { isBoolean } from '../../utils/inspect';
-import { mathMax, mathPow } from '../../utils/math';
-import { toFloat, toInteger, toFixed } from '../../utils/number';
-import { makePropsConfigurable, makeProp } from '../../utils/props';
-import { toString } from '../../utils/string';
-import { normalizeSlotMixin } from '../../mixins/normalize-slot';
-
-// --- Props ---
-
-const props = makePropsConfigurable({
-  animated: makeProp(PROP_TYPE_BOOLEAN, null),
-  label: makeProp(PROP_TYPE_STRING),
-  labelHtml: makeProp(PROP_TYPE_STRING),
-  max: makeProp(PROP_TYPE_NUMBER_STRING, null),
-  precision: makeProp(PROP_TYPE_NUMBER_STRING, null),
-  showProgress: makeProp(PROP_TYPE_BOOLEAN, null),
-  showValue: makeProp(PROP_TYPE_BOOLEAN, null),
-  striped: makeProp(PROP_TYPE_BOOLEAN, null),
-  value: makeProp(PROP_TYPE_NUMBER_STRING, 0),
-  variant: makeProp(PROP_TYPE_STRING)
-}, NAME_PROGRESS_BAR);
-
-// --- Main component ---
-
-// @vue/component
-const BProgressBar = /*#__PURE__*/extend({
-  name: NAME_PROGRESS_BAR,
-  mixins: [normalizeSlotMixin],
-  inject: {
-    getBvProgress: {
-      default: /* istanbul ignore next */() => () => ({})
-    }
-  },
-  props,
-  computed: {
-    bvProgress() {
-      return this.getBvProgress();
-    },
-    progressBarClasses() {
-      const {
-        computedAnimated,
-        computedVariant
-      } = this;
-      return [computedVariant ? `bg-${computedVariant}` : '', this.computedStriped || computedAnimated ? 'progress-bar-striped' : '', computedAnimated ? 'progress-bar-animated' : ''];
-    },
-    progressBarStyles() {
-      return {
-        width: 100 * (this.computedValue / this.computedMax) + '%'
-      };
-    },
-    computedValue() {
-      return toFloat(this.value, 0);
-    },
-    computedMax() {
-      // Prefer our max over parent setting
-      // Default to `100` for invalid values (`-x`, `0`, `NaN`)
-      const max = toFloat(this.max) || toFloat(this.bvProgress.max, 0);
-      return max > 0 ? max : 100;
-    },
-    computedPrecision() {
-      // Prefer our precision over parent setting
-      // Default to `0` for invalid values (`-x`, `NaN`)
-      return mathMax(toInteger(this.precision, toInteger(this.bvProgress.precision, 0)), 0);
-    },
-    computedProgress() {
-      const precision = this.computedPrecision;
-      const p = mathPow(10, precision);
-      return toFixed(100 * p * this.computedValue / this.computedMax / p, precision);
-    },
-    computedVariant() {
-      // Prefer our variant over parent setting
-      return this.variant || this.bvProgress.variant;
-    },
-    computedStriped() {
-      // Prefer our striped over parent setting
-      return isBoolean(this.striped) ? this.striped : this.bvProgress.striped || false;
-    },
-    computedAnimated() {
-      // Prefer our animated over parent setting
-      return isBoolean(this.animated) ? this.animated : this.bvProgress.animated || false;
-    },
-    computedShowProgress() {
-      // Prefer our showProgress over parent setting
-      return isBoolean(this.showProgress) ? this.showProgress : this.bvProgress.showProgress || false;
-    },
-    computedShowValue() {
-      // Prefer our showValue over parent setting
-      return isBoolean(this.showValue) ? this.showValue : this.bvProgress.showValue || false;
-    }
-  },
-  render(h) {
-    const {
-      label,
-      labelHtml,
-      computedValue,
-      computedPrecision
-    } = this;
-    let $children;
-    let domProps = {};
-    if (this.hasNormalizedSlot()) {
-      $children = this.normalizeSlot();
-    } else if (label || labelHtml) {
-      domProps = htmlOrText(labelHtml, label);
-    } else if (this.computedShowProgress) {
-      $children = this.computedProgress;
-    } else if (this.computedShowValue) {
-      $children = toFixed(computedValue, computedPrecision);
-    }
-    return h('div', {
-      staticClass: 'progress-bar',
-      class: this.progressBarClasses,
-      style: this.progressBarStyles,
-      attrs: {
-        role: 'progressbar',
-        'aria-valuemin': '0',
-        'aria-valuemax': toString(this.computedMax),
-        'aria-valuenow': toFixed(computedValue, computedPrecision)
-      },
-      domProps
-    }, $children);
-  }
-});
-
-export { BProgressBar, props };