Henrique Schmaiske and the human work behind Meteor 3.0

Meteor.js is one of those open-source projects developers have lived with for years. It has over 44,800 GitHub stars, more than 500,000 active installations worldwide, and still sits inside products across many countries.

Behind its largest release in over ten years, Meteor 3.0, is Henrique Schmaiske, CTO of Meteor Software, who started the work in April 2022 and led it to release in July 2024.

Meteor launched in 2011, when full-stack JavaScript felt new. Its appeal was straightforward: developers could build across client and server with one language, while working with real-time data patterns that made applications feel immediate.

That is what made Meteor 3.0 more than a routine upgrade. When a framework has over 5,300 GitHub forks and hundreds of thousands of active installations, every major change lands somewhere: on startups, enterprises, and developers relying on maintainers’ decisions.

For Schmaiske, the work was not about making Meteor look new but about moving it forward without treating its community as collateral damage.

The hardest technical issue was Fibers, a library Meteor had used to make asynchronous JavaScript feel synchronous. For developers, it had been part of Meteor’s smoothness, but the JavaScript and Node.js ecosystem had moved on.

The need to remove Fibers had already been written down in GitHub Discussion #11505 in June 2021. That was the original planning document, but execution had not started. Schmaiske began work after joining Meteor as Tech Lead in April 2022.

He led the Meteor.js open-source team, setting direction, designing migration paths, sequencing releases, reviewing code as a CODEOWNER, and communicating publicly with users. The team implemented the changes, while Schmaiske led the effort.

The change touched methods, publications, and database access. Meteor had to move to native async and await while giving applications a realistic way to adapt. When Node.js 14 reached end of life in April 2023, the path became urgent.

Inside a company, a difficult migration can be managed through meetings and deadlines, but open source is different. People are spread across countries, time zones, companies, and priorities. Some teams upgrade quickly, while others have compliance reviews, customer obligations, or production systems where downtime is serious.

That is why communication became part of the engineering work. In March 2023, Schmaiske opened the public Meteor forum thread for the Fibers roadmap and Meteor 3.0, then posted weekly progress updates for nearly 18 months.

Those posts were practical. They showed wha