Schema autocomplete and validation for vercel.json - Vercel You are able to add a schema, but it should be available in node_modules the same way that turbo.json is available in node_modules. This ensures that you always have the version that matches your local vercel npm package version.
Welcome to the community, @jakeleventhal! Thanks for the suggestion.
Can you explain the use case a bit more? I want to make sure I understand what you’re looking for.
1 Like
Hi @amyegan, answering in behalf of @jakeleventhal as I talked to him about this directly
What we’re suggesting is to allow for referencing the vercel.json’s $schema to a local file in package.json, just like turborepo did here in a recent update: Editor integration | Turborepo.
This file could be bundled with the vercel cli package.
There might be reasons why this might not be wanted, since it’s dealing/referencing with the vercel cloud service directly, and not just a local package that exists in the node_modules.
Thank you!
1 Like
Do you mean like this?
@amyegan, yes, but instead of having it be a remote file, it would be available in the “vercel” npm package, so that we could import it from node_moules instead of hitting
openapi.vercel.sh or any other remote file