← All Accelerator Releases
Accelerator 3.0.0
November 11, 2026Nuxt 4.6 baseline, component improvements, and form fixes
Breaking Changes
Nuxt 3 and Nuxt 4.0–4.5 are no longer supported. This release requires Nuxt ^4.6.0. Dropping support for these older Nuxt versions is the reason for the major version bump to 3.0.0.
Added
- Dropdown now supports creating new values in single selection mode with
allowCreate. - DatePicker now supports a custom trigger slot and
v-model:open, while keeping its default Input trigger. - DatePicker's
v-modelinfersstring | undefinedfor single mode andRangeValuefor range and week modes. - Added a SegmentedControl example with custom dates, today, yesterday, last 7 days, and last 30 days.
- Expandable now supports multiple
{ trigger, content }items with shared group styling. - Added numbered slots such as
trigger-1andcontent-1to replace an item's text with custom markup. - Added linting setup documentation and separate Accelerator and linting package histories under Release Notes.
Changed
- Expandable renders from
itemsand uses numbered trigger and content slots. - SegmentedControl uses numbered slots with a hyphen, such as
option-1instead ofoption1. - Server handlers now use Nuxt's
nuxt/serverAPI while retaining Nitro-backed session storage. $accApianduseAccApishare an exportedAccApitype using Nuxt's fetch option types.- The CLI doctor now checks installed dependency versions against the module's supported peer ranges.
- Updated peer dependencies, including Vue
^3.5.44, VueUse^15.0.0, andfocus-trap^8.2.4.
Fixed
- Fixed the CLI omitting Avatar and Tooltip dependencies when adding ProfileAvatar or ProfileForm.
- Fixed authenticated requests failing when another application refreshed a shared session and the backend returned
Unauthorizedfor the previous refresh token. Requests now continue with the refreshed credentials when available. - Dropdown now accepts typed API options with custom
labelKey,valueKey, anddisabledKey, and checks that those keys exist on the option type. - Fixed the Button sizes preview so each size displays at its intended height.
- Fixed Expandable model forwarding so toggling updates its open state correctly.
- Fixed DatePicker range fields storing formatted strings instead of
{ start, end }objects, which caused form schema validation errors. - Input's
displayFormatternow supports raw object values and preservesnullandundefinedwhen initializing or clearing the model, with its argument type inferred from the input model. - Added explicit initial password and remember-me values to LoginForm and an initial password value to RegisterForm to keep form initialization consistent during hydration.
- External
v-modelclears now reset Dropdown and Textarea, set Checkbox and Toggle to unchecked, and clear Radio selection. - Fixed Cosmos DB SDK inclusion in standalone server output when the Cosmos DB storage driver is configured.
Upgrade Notes
- Upgrade to Nuxt
^4.6.0with Nitro^2.0.0and Node.js^22.22.3 || ^24.15.0 || >=26.0.0. Align peer dependencies with the module'spackage.json, then runacc-nuxt doctorto check installed dependency compatibility. - Update the copied Input, DatePicker, Dropdown, Expandable, and SegmentedControl templates together, preserving local customizations. DatePicker's range handling relies on Input accepting raw object values.
- Update the copied LoginForm and RegisterForm templates to fix hydration issues caused by missing initial field values, preserving local customizations.
- Pass one
itemsentry per expandable and use#trigger-1or#content-1for custom markup. - If you use SegmentedControl option slots, rename
#option1,#option2, etc. to#option-1,#option-2, etc. - Expandable manages its own open state by default. Only when controlling it externally, use a boolean array for
v-model, such as[true, false], following item order.
For example, migrate a single Expandable:
Before:
<template>
<AcceleratorExpandable>
<template #trigger>Details</template>
More information
</AcceleratorExpandable>
</template>After:
<template>
<AcceleratorExpandable
:items="[{ trigger: 'Details', content: 'More information' }]"
/>
</template>For custom markup, use #trigger-1, #content-1, and #icon-1 on the new component.
For an Expandable with custom slots:
Before:
<template>
<AcceleratorExpandable>
<template #trigger><strong>Details</strong></template>
<template #icon="{ isExpanded }">{{ isExpanded ? '−' : '+' }}</template>
<p>More information</p>
</AcceleratorExpandable>
</template>After:
<template>
<AcceleratorExpandable :items="[{}]">
<template #trigger-1><strong>Details</strong></template>
<template #icon-1="{ isExpanded }">{{ isExpanded ? '−' : '+' }}</template>
<template #content-1><p>More information</p></template>
</AcceleratorExpandable>
</template>For SegmentedControl, rename #option1 and #option2 to #option-1 and #option-2. Custom slots replace the default label and receive the corresponding option:
Before:
<template>
<AcceleratorSegmentedControl v-model="selected" :options="options">
<template #option1="{ option }">
<AccICalendar /> {{ option.label }}
</template>
<template #option2="{ option }">
<strong>{{ option.label }}</strong>
</template>
</AcceleratorSegmentedControl>
</template>
<script setup lang="ts">
import { ref } from 'vue';
const options = [
{ value: 'day', label: 'Day' },
{ value: 'week', label: 'Week' },
] as const;
const selected = ref<'day' | 'week'>('day');
</script>After:
<template>
<AcceleratorSegmentedControl v-model="selected" :options="options">
<template #option-1="{ option }">
<AccICalendar /> {{ option.label }}
</template>
<template #option-2="{ option }">
<strong>{{ option.label }}</strong>
</template>
</AcceleratorSegmentedControl>
</template>
<script setup lang="ts">
import { ref } from 'vue';
const options = [
{ value: 'day', label: 'Day' },
{ value: 'week', label: 'Week' },
] as const;
const selected = ref<'day' | 'week'>('day');
</script>Slot numbers follow the order of options. Options without a custom slot keep their default label.