[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Feedback](/c/feedback/8)

# Add node_modules exposed schema for vercel.json

136 views · 2 likes · 5 posts


Jake Leventhal (@jakeleventhal) · 2025-02-25

https://vercel.com/changelog/schema-autocomplete-and-validation-for-vercel-json 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.


Amy Egan (@amyegan) · 2025-02-25 · ♥ 1

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.


Gabriel Bianchi (@dbianchii) · 2025-03-03 · ♥ 1

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: https://turbo.build/repo/docs/getting-started/editor-integration#sourcing-from-node_modules.
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!


Amy Egan (@amyegan) · 2025-03-21

Do you mean like this? 

https://vercel.com/docs/project-configuration#schema-autocomplete


Gabriel Bianchi (@dbianchii) · 2025-03-21

@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