Alpine.js on the @NativeScript website?
— Hugo (@hugo__df) January 28, 2021
This email is supported by my GitHub Sponsors.
A pro tip for @Alpine_JS: Its sometimes faster without :key on your `x-for`. Alpine will default to the index, which saves an eval call. However, if your `x-for` data changes state, you should be using a unique identifier so Alpine can properly keep track.https://t.co/ZqeLrArhHn
— Kevin Batdorf (@kevinbatdorf) January 25, 2021
Nice layout tip from Ryan, not for everyone, I’m personally a “write all the code inline” type of person for my demos, but cool setup for those who enjoy a bit more structure (& like Laravel-looking code a bit more than me).
🔥 If you’re using @Alpine_JS and want to keep your components more organised, why not try out a global vendor object that holds all of your component data functions, mixins and helper functions?
(the screenshot is something you might bundle using Webpack or Rollup)
— Ryan Chandler (@ryangjchandler) January 27, 2021
Here are this week’s Alpine.js adopters:
For more posts like these, you can join the Alpine.js Development Subscription, it’s a great way to support the newsletter and get early access to Alpine.js content.
@Alpine_JS Is cleeeeean. Nice work
— Moladukes (@CitrusMe) January 27, 2021
I just heard of Alpine.js when I’m starting to play around with TailwindCSS. It’s lightweight and does the job.
— Namwa (@namwa_swd) January 23, 2021