I grew up watching Dragon Ball Z, and one of the most common tropes was the bad guy’s “final form” moment.
After a tough battle, our heroes were beaten and bruised but had finally gotten the enemy on the ropes. These courageous warriors were almost ready to land the final blow, when the enemy suddenly declared that this wasn’t even their final form, and then launched into a lengthy transformation process that refilled their energy and left them even stronger than before.
Why the bad guy didn’t just walk around in that final form in the first place, or why…
Vulcan is built around the very powerful idea of having a central schema that governs the behavior of your entire app, from the database to your API to forms.
But the downside of this approach is that up to now, there was no elegant way to get more granular and specify server-only, database-only, or API-only fields.
To illustrate the issue, imagine you want one of your API fields to hit the Stripe API: you won’t be able to define this field in the same place as the rest of your shared schema, since it will call a server-only Stripe npm…
But first, to celebrate this fourth version I want to take a look back at how Sidebar’s design has evolved since its start all the way back in 2012:
I recently deployed a new version of Sidebar, and even though I’ve deployed Meteor apps countless times before, I still ended up with a lot of misconfigurations, crashes, and downtimes.
So to save myself (and maybe you as well!) a lot of pain in the future, I’ve decided to recap here the most common issues when deploying a new Meteor app.
I’m going to guess that the past few weeks have sucked for pretty much everybody reading this. But in a way, open-source software can be a unexpected escape from the daily grind.
Fixing bugs and refactoring React forms might not sound like the sexiest thing ever, but it’s a nice way to feel like you’re making progress on something and find a little bit of normality in a constantly changing world!
Here’s what’s new in the latest Vulcan release.
A big change in Vulcan 1.15 is how field-specific data loading is handled. …
Vulcan 1.14 brings a rethinking of the APIs for the entire data flow, from server to client.
These new APIs exist in parallel to the old ones, meaning you can progressively switch whenever you’re ready to take advantage of the new features.
Some of Vulcan’s own components have been ported to the new APIs (such as the Datatable component) while others will remain on the old APIs for now. Vulcan’s back-end layer on the other hand will be compatible with both APIs:
As you can see, while HoCs and hooks have separate versions for the old and new APIs (which…
Disclaimer: these are my personal views, and I have no relation with either Tiny or MDG. So take this entirely unofficial opinion with a grain of salt.
Meteor.js was first unveiled publicly in April 2012. Six months later, I started writing a book about it with Tom Coleman, the main creator of (among many other things) Meteor’s package management ecosystem.
That book, Discover Meteor, went on to become the main reference for the growing Meteor community and became my main focus for the next few years, spanning countless updates, blog posts, podcasts, and even a very cool t-shirt which I…
git pullfrom the Vulcan.js repo (
Apart from updating the Vulcan codebase, you’ll also need to update the NPM packages it depends on. Here’s an overview of what’s new and what needs to be updated.
You can update all your NPM packages by 1) copying the Vulcan-Starter package.json file into
.vulcan/package.json and 2) running the following command from your app’s directory:
meteor npm run update-package-json
Note: if the script is not available, add the following line to your
I’ve been using CSS for 10+ years, so I know it pretty well by now. I can handle flexbox, I’ve mastered SASS, and I even know the difference between ems and rems.
But wait, now there’s Grid, too? And position: sticky? And what’s this I hear about this CSS-in-JS thing?? Turns out, maybe I don’t know CSS that well after all…
If you’re feeling the same, first let me just say that this is entirely normal. CSS has been evolving at record speed lately, and even the most dedicated developer can fall behind if they’re not careful.
We judged the entries according to three main criteria: