feat(Codemod) : Meteor Migration v2 -> v3 [adding remaining codemods and migration recipe]

[Yugal41735]

Call to CallAsync

Due to how meteor now work withasync/await this codemod transforms call to callAsync.

Here is the codemod:

1. https://go.codemod.com/QADwWlx

Meteor.userAsync

This codemod transforms Meteor.user to Meteor.userAsync.

Here is the codemod:

1. https://go.codemod.com/QADwWlx

Meteor/V3/Add Await To Async Webapp Methods

This codemod adds await to the webapp methods which are now async

1. https://codemod.com/registry/meteor-v3-add-await-to-async-webapp-methods

Meteor/V3/Update React

This codemod helps in transforming react to meteor

1. https://codemod.com/registry/meteor-v3-update-react

[vercel[bot]]

@Yugal41735 is attempting to deploy a commit to the Codemod Team on Vercel.

A member of the Team first needs to authorize it.

[mohab-sameh]

@Yugal41735 We're moving codemod packages to their corresponding owners so it's easier for codemod owners to own and maintain their codemods, and be notified about any issues in their own repos. Do you mind moving this to your own repo and updating the GitHub source URL of the published codemod to point to your github repo?

1. Create a repo in your own GitHub account and move the source code of your codemods to that repo.

   • This will drive more traffic to your profile and clarify ownership, increasing visibility and transparency.
   • You could name the repo something like codemods (or choose a name you prefer).
   • For the README of that repo, you can use a format similar to what's in the commons repo.

2. Update the git URL in the codemods’ metadata to your new repo and bump their versions.

3. Republish the codemods to ensure they are showing the correct git URL in the registry.

4. Optionally, you can duplicate this GitHub Action for your repo. This way, every time you make a change to one of your codemods and merge the code to the main branch, it will automatically publish the codemod for you.