Thank you for making this extension! I have one request: to have options added to the command palette for "Open in Vercel:"

• Project
• Deployments
• Current Deployment
• Logs
• Project Settings
• any other links you think would be useful

Similar to the "Open in Github" extension:

Hello,

From the status bar I see ▲ Loading and the tooltip says "Loading Vercel deployment status..."

Access token is set. Project is correctly linked.

Any idea why it's stuck on loading?

Thanks!

The Issue:

The extension in its current form is incapable of utilizing the project.json file injected into any workspace using the Vercel CLI, therefore forcing the user to define a redundant settings.json file in any workspace they would like to use this extension in.

Solution:

Check the workspace for a .vercel/project.json file, which is an ordinary JSON file(not JSONC), and thus can be easily parsed with JSON.parse, and use the projectId value from it if applicable.

Problems with this solution:

Subdirectories are not searched, and thus, if a user uses vercel DIRNAME instead of the root directory of the workspace, this approach will not detect the file. However, this problem is trivial with the combination of the project setting, which could allow for either a fallback or override value to the value found in the JSON file.

Solved by:

Pull Request #16

Additional considerations(mostly irrelevant to this request):

the project setting should be renamed or better documented. As a user of the extension, I originally thought it to be broken due to my misuse of this settings. I placed my project name (ie YOUR-PROJECT) when it should be a project id (ie prj_89au98uf0), this is not very well documented beyond the fact that the example code begins with prj_; however, to a new user, that may be misunderstood as simply part of the demonstration value.

I often see errors from vercel-vscode when resuming my laptop (running macOS Sonoma) & VS Code (1.84.2).

They typically look like this:
request to https://api.vercel.com/v6/deployments?projectId=prj_uw47ou5Nsqxw4O8s4fpp2hDD3G1L&limit=1 failed, reason: getaddrinfo ENOTFOUND api.vercel.com

and

invalid json response body at https://api.vercel.com/v6/deployments?projectId=prj_uw47ou5Nsqxw4O8s4fpp2hDD3G1L&limit=1 reason: Unexpected token 'A', "An error o"... is not valid JSON

In a big slew like this:

I get that these are "expected" in that these are network requests being made and are failing. Eventually, it connects and the extension is happy.

I'm wondering if there's a potential change in behaviour here that could reduce or avoid these.