Also I ran this below… and it gave a few warnings, but how do you go about to find and fix whatever is wrong from the warning??? This might be a tangent issue as of right now I am looking to deploy a private repo.
PS D:\EdgarLindo\things\Stuff\Acode\emails> npm install --global vercel
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
It looks like you ran into a few different problems. Sorry this process has been so difficult for you.
If you want it to deploy automatically whenever you push changes to your GitHub repo, then you’ll need to connect the repo to your Vercel project. You’ll also need to make sure the metadata on the commit matches up with your GitHub and Vercel accounts.
When you deploy with the CLI for the first time, it should present you with a prompt to choose a new or existing project. But you can also use the vercel link command to link a local directory to a Vercel project.
The docs have more info about deploying private repos:
Please let me know if you’re still having trouble after updating git metadata and reviewing the documentation. We can dig into this together and figure out why it’s not working for you.