Vercel no longer supports configuration files named now.json. Builds that still use this old name will fail. Simply rename the file to vercel.json and everything will work again.
When you try to build, you’ll see a warning like this:
Warning: “now.json” is deprecated and no longer supported.
Vercel has completely dropped support for the now.json filename. You must rename it to vercel.json.
Here’s the full error message:
|
|
Interestingly, the linked documentation doesn’t specifically mention that now.json is no longer valid — it only states that the configuration file should be named vercel.json, vercel.toml, or vercel.ts.
The fix is simple: just rename your now.json file to vercel.json. You don’t need to change any of the content inside the file.
After you push the renamed file and redeploy, the error will disappear.
File-based configuration
File-based configuration lives in your repository and gets version-controlled with your code. You can usevercel.jsonorvercel.tomlfor static configuration, orvercel.tsfor programmatic configuration that runs at build time. The static formats support the same properties, whilevercel.tslets you generate configuration dynamically using environment variables, API calls, or other build-time logic. You can only use one configuration file per project.
Reprinted from: Yijile.com( https://yijile.com/en/warning-now-json-is-deprecated-by-vercel/ )
Licensed under
CC BY-NC-SA 4.0
.
Please credit the source and link to this article, indicate if changes were made, and share under the same non-commercial terms.