Yeah, there is already an existing meteor-testing skill, though it is currently focused on the standard testing approaches we have in Meteor today with Mocha and Tinytest. Once the work on Rstest and the modern test runner is in place, the skill will be updated to default to the modern approach and guide everybody through its usage and benefits.
react-native is not the officially recommended way for native development in Meteor, at least not at this moment. I really encourage anybody with experience using it to contribute community package docs to the repository so that others can learn how to achieve that.
Is react-native a working and maintained solution in the Meteor 3 era? If that’s the case, let’s honor that work and capability.
If react-native gets at least the status of a community-recommended package, we can include it within meteor-community-packages and the upcoming meteor-native AI skill.
Regarding native development, we will surely cover CapacitorJS integration first, as the most natural path coming from CordovaJS and keeping a single web codebase deployed cross-platform. The meteor-native AI skill will cover it strongly. For any other approaches, we recommend collaborative community work towards documenting and promoting them.
We are making strong efforts in parallel to ensure we cover the minimum overhaul of what Meteor has always been about, including testing and native development, along with the AI utilities that are shaping development these days. With all these pieces, Meteor can continue to be as fun and strong as it was conceived to be.
I hope we can count on your support with early testing, feedback and contributions on everything delivered, which is so important for proper stabilization and collaborative work.