Hello, I’m glad to announce that I’m joining Meteor as Developer Evangelist!
I’ve been working with Meteor for a long time and I’m excited about this opportunity. It will be a great challenge as well as a fantastic time and I’m happy because I know I can count on the Meteor community.
My goal is to be a bridge between the community and the Meteor core team in every way possible. I will also help to create content to promote Meteor, participating in meetups, facilitating community work on Github issues and PRs, and anything else necessary to enable the Meteor community to be active in its platform development.
And as many of you know, Meteor 1.8.2 will be coming out soon, check out PR #10522. Thanks to all 35 participants involved in this PR so far.
A few highlights of 1.8.2:
a) full server restart will be avoided when no files used by the server bundle changed PR #10541
b) New TypeScript-based Meteor application template:
meteor create --typescript new-typescript-appPR #10695
c) improve dynamic module behavior for large projects using many custom local packages, mixing nested and dynamic imports PR #10730
d) ability to run multiple Cordova apps are built from the same application source code at the same time on iOS by selecting a different port using
If you are asking, “How can I help?” here is your answer, you can test your application with this Meteor version and provide feedback, follow these steps to run your application using the release candidate 4 of 1.8.2:
1 - Commit and push any pending change in your local workspace. Create a new branch then you can merge it later when 1.8.2 final is out.
2 - Execute the
Migration Steps in your new branch https://github.com/meteor/meteor/blob/release-1.8.2/History.md#migration-steps, they are just two commands for this release:
If you use npm to manage your npm packages:
meteor npm install @babel/runtime@latest meteor npm install meteor-node-stubs@next
Or if you use yarn:
meteor yarn add @babel/runtime@latest meteor yarn add meteor-node-stubs@next
3 - Make sure your packages are up-to-date:
meteor update --all-packages
See the upgraded packages and read each package release note carefully
4 - Update Meteor to the latest Release Candidate by running this command in your new branch:
meteor update --release 1.8.2-rc.4
5 - Run your app, as usual, if you find any issues, please comment in the PR #10522
Disclaimer: Please don’t use this release candidate in production as it is not a final release.
I’m here to help
If you have any problem with Meteor, or a pending issue, or an unanswered PR, please reach out to me, I’m here to help and I’m open to suggestions so please don’t be afraid to share your ideas with me and the community as a whole.
Also, if you want to share your story with Meteor, please contact me. We can work together and publish your story. We not only welcome business and technical success stories but we also want to hear about your personal success stories.
You can contact me here in the forums or on Twitter @FilipeNevola (my DMs are open) and remember, you are the real Meteor champions, my role here is to remove blockers and help!
Last but not least, I would also like to encourage every Meteor developer to join our Meteor Community Slack channel by following this invite, this Slack was created by the community (thanks Kelly Copley @copleykj) and it is a wonderful place to meet Meteor developers and exchange experiences.
We are starting a new chapter in Meteor history and everyone is invited to be a part of it.
Spread the word
Retweet this announcement and please follow Meteor on every platform: