Field notes from working on production Meteor apps.
September 21, 2026 · InterstellarBits
Most Meteor apps keep their data rules in SimpleSchema and Collection2, with hooks running inside Fibers. Here is how that layer behaves under Meteor 3, how to tell what your schemas are actually enforcing, and how to make the validation portable if you later move off Meteor.
Read moreSeptember 21, 2026 · InterstellarBits
Uploads are the part of an old Meteor app that quietly holds the most risk: an unmaintained package, binary data inside MongoDB, and URLs that customers have bookmarked. How we inventory it and move storage without breaking a single link.
Read moreSeptember 21, 2026 · InterstellarBits
Scheduled tasks are the part of a Meteor app that breaks quietly during the async migration. An inventory-first plan for synced-cron, job queues, and the nightly script nobody owns.
Read moreSeptember 18, 2026 · InterstellarBits
Most production Meteor apps we inherit have almost no tests, and the async migration is the worst time to be guessing. A practical order for adding coverage: methods and publications first, browser paths second, CI last — and how to keep the suite running while the app converts to async/await.
Read moreSeptember 17, 2026 · InterstellarBits
Meteor's client-server wiring makes some mistakes easy to make and easy to miss. A concrete review order for an app you did not write: allow/deny leftovers, unvalidated method arguments, over-publishing, DDP rate limits, and the new class of bugs a missing await creates.
Read more