As you might’ve heard, Meteor 1.0 is right around the corner. And in anticipation of the big release, we’ve just pushed our biggest update (version 1.6 of the book) in over a year.

Read on to find out what’s new, or go check out the book now.

General Changes

We did a ton of general tweaks, fixes, and edits. We updated Microscope to use Bootstrap 3, we moved the collections directory inside lib, we updated our syntax whenever needed, and a lot more…

We also reworked many chapters, including Collections, Creating Posts, and Creating a Meteor Package.

You can read the full changelog to see what’s new.

Better Errors

Apart from that, one of the main things we improved is how we handle errors in the Errors chapter. When we first wrote Discover Meteor, our main goal was to show you how to build a real-world, production-ready app.

And since Meteor was so new at the time, our conception of what a “real-world app” should look like was based on what we already knew. Namely, traditional Rails, PHP, or Node.js apps.

So we naturally decided to display errors in a fixed zone at the top of the page, and clear them when the user left the page:

Errors: the old way.

But this whole concept of “page” doesn’t always make sense in a single-page app. And we encountered problems, such as what to do when we wanted to display an error after the user had left the page.

So for this new version, we scrapped the old-style errors in favor of Growl-like notifications, which ended up being a lot simpler to implement than the previous system:

Errors: the Meteor way.

These errors stay on-screen even if you navigate to another page, and then automatically disappear after a few seconds.

And while we were at it, we also decided to show you how to do in-form validation and error messages.

In-form validation messages.

This was a good lesson for us: rather than fight to make Meteor behave like its older siblings, it’s sometimes much easier to just embrace a new way of coding.

A Note for Translators

If you’re part of our translation teams, we suggest checking out the diff on GitHub (private repo) to get an overview of all the changes, chapter by chapter.

Looking Towards 1.0

All throughout this adventure, we always kept Meteor 1.0 in mind as a goal of sorts. Meteor would finally be ready for primetime, and our book would finally be done.

But the closer we actually get to 1.0, the more we realize it’s not an end goal, but a starting point.

In the 15 months since we released the book, Meteor has changed dramatically, the community has released a ton of amazing packages, and mobile development with Meteor has taken off in a big way.

The result is that we now have a Trello board full of blog post concepts, potential topics for new chapters, and side project ideas. So it looks like this is only the beginning after all!