Alpine: x-spread example on documentation does not work

[oguzhancelikarslan]

the example related to x-spread on documentation does not work.

[SimoTod]

https://codepen.io/SimoTod/pen/gOrgLda 🤔
Make sure you are using the right version. x-spread was added in v2.4.0 as per release notes (https://github.com/alpinejs/alpine/releases)

[oguzhancelikarslan]

Ah, thank you! I was using v2.3.5. can you add a note to documentation saying you should be using v2.4.0 or high?

[HugoDF]

Maybe we should update the pinned version in the README (for prod usage) to always be latest, sounds like a lot of people pinned to 2.3.5

[SimoTod]

We would be back to having to update the readme every release.
Unless we remove the example.

[oguzhancelikarslan]

@HugoDF I contacted with Simone Todaro yesterday. I prepared and shared the first Alpine JS Course in Turkish. and It almost completely contains every piece of documentation. To talk about it can you send me mail! [email protected].

The link: https://www.youtube.com/watch?v=CZloxR3pGwg&list=PLNqIPgpISSa8Yl04SvV2zTCnbp79A4mtH

[ryangjchandler]

@oguzhancelikarslan Could you please discuss this elsewhere.

[ryangjchandler]

@HugoDF I wonder if there is anything that we can automate for this, similar to how we replace the version in the distribution files, perhaps something on release. Or we go back to the old 2.x.x version in the README and make the note about pinning to a version in production more important.

[oguzhancelikarslan]

@oguzhancelikarslan Could you please discuss this elsewhere.

Sure. But I could not find the email address of @HugoDF. Sorry if I disturb you.

[HugoDF]

@HugoDF I wonder if there is anything that we can automate for this, similar to how we replace the version in the distribution files, perhaps something on release. Or we go back to the old 2.x.x version in the README and make the note about pinning to a version in production more important.

As part of the build script we could replace the pinned version with what's in the package.json

[ryangjchandler]

@HugoDF I wonder if there is anything that we can automate for this, similar to how we replace the version in the distribution files, perhaps something on release. Or we go back to the old 2.x.x version in the README and make the note about pinning to a version in production more important.

As part of the build script we could replace the pinned version with what's in the package.json

Yeah, that could work - just a simple string or RegEx replace I guess.

[HugoDF]

Closing this since x-spread is available as long as you're beyond 2.4.0 (have also sent in a PR that will update the README to latest package version so people grabbing the latest version from README should get all the documented features).