From a57a90c9c0d99f00855c301cb9b3cca0708dfdbe Mon Sep 17 00:00:00 2001 From: jbranchaud Date: Thu, 12 Nov 2020 12:31:22 -0600 Subject: [PATCH] Add Naming Of The Vercel Config File as a vercel til --- README.md | 3 ++- vercel/naming-of-the-vercel-config-file.md | 17 +++++++++++++++++ 2 files changed, 19 insertions(+), 1 deletion(-) create mode 100644 vercel/naming-of-the-vercel-config-file.md diff --git a/README.md b/README.md index ad0a4ff..d1bbf27 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ and pairing with smart people at Hashrocket. For a steady stream of TILs, [sign up for my newsletter](https://tinyletter.com/jbranchaud). -_958 TILs and counting..._ +_959 TILs and counting..._ --- @@ -938,6 +938,7 @@ _958 TILs and counting..._ ### Vercel - [Add Web Server Layer Redirects](vercel/add-web-server-layer-redirects.md) +- [Naming Of The Vercel Config File](vercel/naming-of-the-vercel-config-file.md) ### Vim diff --git a/vercel/naming-of-the-vercel-config-file.md b/vercel/naming-of-the-vercel-config-file.md new file mode 100644 index 0000000..72e8db4 --- /dev/null +++ b/vercel/naming-of-the-vercel-config-file.md @@ -0,0 +1,17 @@ +# Naming Of The Vercel Config File + +[Vercel](https://vercel.com/), the company/service, used to be called Now. With +any renaming comes some consistency challenges, even at the level of software. + +The naming of the file for configuring your project used to be `now.json`. It +is _now_ `vercel.json`. + +For [backwards compatibility +reasons](https://vercel.com/docs/platform/frequently-asked-questions#conflicting-configuration-files), +you can still use either. You cannot and should not have both though. + +If you're working with an existing project that uses `now.json`. It is fine to +continue with that naming. It may eliminate some future confusion if you are to +rename it to `vercel.json`. If you're starting a new project, I'd recommend +using `vercel.json`. All the documentation you'll read uses this newer naming +convention.