As everyone knows, Meteor 3 is officially released, and we are already seeing a ton of support in the community and increased contributions. The positive (and negative) feedback is highly appreciated and valuable, and we are moving towards the renaissance of Meteor.js. Whoever wants their ideas heard, even the crazy ones, feel free to contact me or the team directly via Forums or Discord.
It had been a while since we made a major release, so we needed a few more quick RCs and a patch. We had some issues regarding subscription authentication and resolved that quickly in a few betas for 3.0.2. The latest one being 3.0.2-beta.4.
Our backlog for the current release is almost done, so we should expect 3.0.2 sometime next week. With that, we’ll fully tag Meteor 3 as recommended in our release system.
Now, we are in a very good position to keep up with the latest technologies and APIs, simplify the core, and improve the developer experience. If you were in love with Meteor in the past, now is the time to return.
Remember that Meteor.js is way bigger than the core team or a single company and that everyone can contribute and help make it better. I know it can be daunting to work on the code in the core due to its architectural complexity, so we plan to organize live coding sessions explaining how it works. The format of those sessions will evolve naturally as we get more feedback.
No single person can understand everything that goes on inside Meteor, and that is completely fine for making an impact. So, a good place to start would be a high-level map where we can deep-dive into specific areas in the future.
We are a community, and we help each other, complement each other’s strengths, iron sharpens iron… and so on.
As Caesar in Planet of the Apes says:
[…] “apes alone… weak”, but “apes together strong”.
So, to rephrase in our language:
const people = 'Community'
const tech = 'Meteor.js'
return (people > tech) && (tech === Math.pow(people.length, 2))
Tasks and fixes for the next, Meteor 3.0.2 release.
- Remove pinned version of packages inside the skeletons
- Merge
release-3.0intodeveland safekeep v2 branch - All documents still removed upon subscription update/addition
- Review and update migration guide
- Make information about git cloning clearer in 3.0 CLI
- Maybe deprecate Meteor.user() in the server
- Improve Meteor.applyAsync doc
- Fix AppVeyor CI
- Investigate accounts authentication issue with Meteor 3 (subscription related)
- Investigate and optimize subscriptions being recreated after login call (fix for all subscriptions)
- Review v3 docs and update old version references
- Update README for NPM
- Merge 2.x.x to devel/release branch
- Review packages with deprecation warnings when we install Meteor 3
- Investigate setx issue and meteor install on Windows
Meteor 3.0.2 is expected to arrive next week.
Next Releases
- Meteor 3.0.3 (Late August, 2024)
- Meteor 2.17 (Mid-September, 2024)