A branch is already available for the likely 2.16.2 release, including Cordova 14 support. We successfully patched cordova-android to remove Node 16 API usage, since Meteor 2 still uses Node 14 and can’t resolve behaviors like the recently introduced copySync and fsp.copy APIs. As I was afraid of, we had to fork cordova-android and maintain a new version of this package. I was able to test it and the Meteor Cordova app runs successfully.
Now we need to release Meteor 2.16.2 for everyone to use. However, this has become a slow and manual process. Our CI isn’t as ready as Meteor 3 to publish new releases, and we expect to need some time to make it available. I can’t give dates yet.
What you can do now is start using a Meteor checkout to run and build your app. Clone the meteor/meteor repo, switch to release-2.16.2, then use <path-to-meteor-clone>/meteor <run|build|...> as your CLI to work with your Meteor app. This way you’ll get unblocked and be able to run and publish your Cordova app with latest SDK expectations. It’s also a way to double check and verify, which we appreciate.
I won’t stop insisting though that this is likely the last time we revisit Cordova in Meteor 2. Your migration to Meteor 3 is becoming urgent, so we can focus on Meteor 3 and bringing you not only the latest Cordova updates, but also next-generation tools for native integration like CapacitorJS.
If you have migration troubles, ask in the forums about them. I’ve also finished my Meteor 3 migration recently, even reviving a package that was blocking me. It’s now a major priority for every Meteor developer and company.
