If you missed it on Twitter/GitHub, this week’s Alpine.js release (2.8.0) adds better error messages when Alpine.js hits an eval error. It uses
console.warn under the hood so you might want to display those when working on an Alpine.js project.
Sample error messages:
This email is supported by my GitHub Sponsors.
This will be the last issue of the newsletter for 2020, I’m taking a break until the New Year, if you’ve got anything to share, make sure to submit your link and happy holidays to everyone in the Alpine community.
Quick TailwindUI tip for alpine users:
If you are also too lazy to add the transitions yourself. Go into the element inspector in your dev tools and copy them directly from the HTML. pic.twitter.com/1k70xIPuFh
— 𝗙𝗲𝗹𝗶𝘅 𝗦𝗰𝗵𝗼𝗹𝘇 💻 (@scholz_felix) December 18, 2020
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 devtools v0.1.0 and v0.1.1 are out, you can now access component instances in the console and we’ve fixed a bug around Alpine version detection is not latest and upgrade to Alpine.js 2.8.0. For Chrome and Firefox (by @hugo__df).
x-fortemplates were sharing DOM nodes
Refactoring Vue components into @Alpine_JS has become my new favorite pastime. Deleting whole files of code is so much more satisfying than writing them in the first place.
— Cameron Scott (@CameronHScott) December 12, 2020
Good luck to @joelvarty for his JAMstack Lagos presentation.
I love technology
— Joel Varty (@joelvarty) December 11, 2020