I appreciate all the work that everyone in the core team is doing to handle the release of Meteor 3.0. At the same time, I love the loyalty and commited community based on the love for the tool. The open to speech and proactive spirit define us on our endevors to keep using Meteor in our daily basis, whether it’s in the form of personal usage or through invaluable contributions such as packages and enhancements. We should not lose the focus on that no matter which are the circumstances and reactions around us.
I am excited and motivated on Meteor 3. I started to use it locally. In fact, I wish go further and start provinding some adaption to community packages, to not use fibers anymore.
I created a small app using Meteor 3, and I realized that tests are not working properly. We are missing the adaption of test packages there. Tests are an essential part to adapt the rest of packages, since almost all them involve to run tests to verify the behaviors are still working.
I did some changes on test packages to be fiber-free and I was able to pass properly the tests for an example app as you can see in the picture below.
I am not sure if it will cover all scenarios. Surely, there is more to adapt, like test coverage and may others, this is just a start. But the simple test capability may be adapted with a minor change I could commit for review.
My questions are:
- Is anyone already in charge of the testing part? Is it planned or already tackled by the core or any community member?
- How would the procedure be to start contributing with the changes on the packages?
I believe these are the next steps to define in order to get more people involved on this migration.