Skip to content

Releases: alpinejs/alpine

v2.8.0

15 Dec 17:26
Compare
Choose a tag to compare

Added

  • Better error messaging #887

Fixed

  • Directly adjacent x-for templates were mistakenly sharing DOM nodes #851

v2.7.3

27 Oct 17:51
Compare
Choose a tag to compare

Fixed

  • Nested transitions wrapped with parent x-shows were being abruptly ended if the transitions were interrupted #853

v2.7.2

22 Oct 14:51
Compare
Choose a tag to compare

Fixed

  • Regression where x-for when used with an array of a single number caused issues #840

v2.7.1

20 Oct 19:25
Compare
Choose a tag to compare

Added

  • .$watch now supports watching magic properties #767

Fixed

  • Checkboxes using x-model were checking for strict equality which causes bugs with arrays containing a mix of strings and integers. Now using loose-equality check #815
  • x-spread didn't support "leave" transition directives #802
  • magic properties now support IE11 #771
  • Checkboxes with non-boolean :value bindings were being treated as booleans (for example the integer "0") #770
  • x-for="i in 10" currently works (looping a range 1-10), however x-for="i in count" (if count were 10) didn't - fixed now #761

v2.7.0

09 Sep 16:17
Compare
Choose a tag to compare

Added

  • Adds support for ranges in x-for: x-for="i in 10" #748

Fixed

  • IE11 was getting "multiple root in x-for" warnings #715
  • $watch() now supports array mutations (like push, pop, etc...) #719
  • x-text wasn't working on SVG elements because we were using .innerText and not .textContent #736

v2.6.0

14 Aug 15:15
Compare
Choose a tag to compare

Added

  • Support for await inside event handlers. (Now run in an async context) #705

Fixed

  • Support .camel modifier for namespaced events: x-on:ns:event-name.camel.window="foo = 'bob'" #664
  • Allow numbers in bound attributes (helpful for SVG properties like x1) #667

v2.5.0

20 Jul 14:58
Compare
Choose a tag to compare

Added

  • Added .camel modifier to allow binding to events and properties using kebab-case but converting them to camelCase before binding. For example: x-on.some-event.camel will listen for an event called "someEvent". #597
  • Added .passive event listener modifier to increase scroll performance. (forces browsers to not block scrolling for event handlers) #619

Fixed

  • Fix a bunch of little transition bugs. #623
  • Pass an $event object to event handlers bound with x-spread. #636
  • Force a consistent order of processing for x-show and x-model to prioritize them over manual :style bindings #659

v2.4.1

21 Jun 13:16
Compare
Choose a tag to compare

Fixed

  • Changes introduced by #543 caused regressions in x-show within x-for directives. It has been reverted.

v2.4.0

18 Jun 17:22
Compare
Choose a tag to compare

Added

  • x-spread directive (Allows you to bind an element to an object of Alpine directives and they will be "applied" (similar to x-bind="{}" in Vue)) #515
  • Now if one Alpine component on a page breaks, the others still work #447
  • You can now access $el from an x-data expression #479
  • Add support for animations in x-transition directives #498
  • x-model.number is now supported for checkbox arrays (all items will be cast to a numeric value) #558

Fixed

  • $nextTick now waits until a transition is completely started (an extra tick) until being called #555
  • Because attributes are ALWAYS set in Alpine, some elements like "" were being interupted. Now only if the attribute has CHANGED will it be set #550
  • If transitions are toggled too fast, there would be race conditions. Now overlapping transitions is supported (the previous transition is finished first before the next one is applied) #543
  • Allow nested components to be moved around the DOM and not be re-initialized #449
  • Checkboxes were being checked by default if a value binding was present #462
  • Expressions that use a "result" variable were running into a conflict with Alpine's built-in result variable. "result" is freed up now #505

v2.3.5

15 May 15:23
37151dd
Compare
Choose a tag to compare

Fixed

  • Elements with x-transition:leave-* and no enter transition were being "shown" one tick after $nextTick, even though there is no transition for them. This is fixed. #492