Skip to content

Releases: Atmos4/van-element

v2.0.0

17 Jul 16:45

Choose a tag to compare

Van Element 2.0 is out ☀️

Breaking changes

  • removal of children property

Although it was nice to have a polyfill for the Web Component slot, it was not working properly when new elements were added after the custom element was defined.

For this reason and in order to not cause confusion and drift away from the Web Component specification, the children polyfill is being removed. You can replace it by van.slot() when the Shadow DOM is enabled, and by VanJS code when it isn't.

This is the only breaking change.

Improvements

The mount function can now be called many times, which allows the introduction of custom hooks 🎉

Bundle size

Bundle size has decreased to 295 bytes 🤏

v1.0.0

04 Apr 15:31

Choose a tag to compare

I am happy to announce Van Element's main release 🎉

Documentation: https://van-element.pages.dev/
Showcase on Codepen: https://codepen.io/atmos4/pen/ZEPEvvB

Van Element is a lightweight wrapper that makes it simple to create reusable custom elements with VanJS!

It features everything you would find in VanJS on top of:

  • reusable components
  • easy hydration thanks to native custom elements
  • reactive attributes
  • lifecycle hooks

It also allows to leverage the Shadow DOM for fully isolated Web components... or disable it completely without sacrificing any of the above benefits👌

If you are interested about the project, don't hesitate to post an issue if you find a bug or if you just have a question! Contributions are also most welcomed 🤗

0.2.4 - First alpha release

07 Feb 13:14

Choose a tag to compare

Pre-release

van-element is now stable enough to release a first alpha version!

Documentation: https://van-element.pages.dev/
Showcase on Codepen: https://codepen.io/atmos4/pen/ZEPEvvB

Van Element is a lightweight Web Component wrapper that makes it simple to create reusable custom elements with VanJS 🎉

There is still some work to be done before v1.0.

  • The library needs to be properly tested.
  • Documentation has to be polished, and a proper example page needs to be created.
  • The API needs better Typescript support and could change quite a bit as a result, with a goal of staying under 1kB.

If you are interested about the project, contributions are most welcomed!