Flickity v3 quasi-released

[desandro]

Heads up: This weekend I released a new major version of Flickity, v3.0.0. The code is up on GitHub, but there is still plenty more work to be done: updating add-ons like flickity-fullscreen and then updating the Flickity documentation site.

I recommend you continue to use Flickity v2 and its supported add-ons. When v3 is completely ready, I'll let you know.

Best,
Dave

[S-n-d]

Just wanted to say THANK YOU for all the hard work. ❤️

[yaodingyd]

You are the best, Dave!

[realchriswells]

Does it self-destroy if it is showing all available slides on one screen?

I've tried draggable but that doesn't do what I need, neither does watchCss. I believe I've got quite the edge-case where I'm showing several carousels on one page and they are built up from the same source, but might have different numbers of elements inside of them within the carousel.

[derWebdesigner]

@desandro Is there any update on this? Can't wait to try the new version since v2 seems to have issues with Safari for a few months. Would happily pay for the new version again but some info on the timeline would be great because of the current issues I would have to switch to SwiperJS otherwise.

[RyanofWoods]

In my opinion, I think it would be beneficial if these quasi releases would instead use some beta release semantics by using rc, alpha and beta in the version tag, and by not setting the NPM package's default to these versions. This would allow users to test out these versions if they wish and that developers/dependabot don't bump to unstable quasi releases unknowingly. The fact that 3.0.0 is a quasi release is quite hidden, as it's in the issues section, and there's no changelog for the release yet.

Our team thought 3.0.0 was a normal release but was not documented yet, so we had to pull Q/A on it, where it failed 🙁

What do you all think? 🙂

[coreyworrell]

Yeah, very frustrating to not be able to update npm dependencies either as normal, have to remember each time to update everything except flickity. It's been in this state for almost a year now.

[razaanstha]

@desandro. any updates on this; the npm library is installing the quasi release of v3 instead of the stable release v2? Also the documentation is still not yet released for the v2?

[mylastore]

How to install version 3 latest build ?

[Webmaster-Siag]

How to install version 3 latest build ?

Put this in the head:

<link rel="stylesheet" href="https://unpkg.com/flickity@3/dist/flickity.min.css">
  <link rel="stylesheet" href="https://unpkg.com/flickity-fullscreen@2/fullscreen.css">

And this in the body:

  <script src="https://unpkg.com/flickity@3/dist/flickity.pkgd.min.js"></script>
  <script src="https://unpkg.com/flickity-fullscreen@2/fullscreen.js"></script>