From c732c65f6039c71891d054c3e4708d79904ba269 Mon Sep 17 00:00:00 2001 From: JJ Kasper Date: Wed, 23 Jun 2021 11:20:28 -0500 Subject: [PATCH] Update next-env note in docs (#26536) This ensures we don't recommend editing the `next-env` file since we need to be able to tweak it to accept future types we add in Next.js ## Documentation / Examples - [x] Make sure the linting passes Closes: https://github.com/vercel/next.js/issues/26533 --- docs/basic-features/typescript.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basic-features/typescript.md b/docs/basic-features/typescript.md index 2dcee6912d9b0..9c7d14640276a 100644 --- a/docs/basic-features/typescript.md +++ b/docs/basic-features/typescript.md @@ -53,7 +53,7 @@ npm run dev You're now ready to start converting files from `.js` to `.tsx` and leveraging the benefits of TypeScript!. -> A file named `next-env.d.ts` will be created in the root of your project. This file ensures Next.js types are picked up by the TypeScript compiler. **You cannot remove it**, however, you can edit it (but you don't need to). +> A file named `next-env.d.ts` will be created in the root of your project. This file ensures Next.js types are picked up by the TypeScript compiler. **You cannot remove it**, and it should not be edited as it can change at any time. > TypeScript `strict` mode is turned off by default. When you feel comfortable with TypeScript, it's recommended to turn it on in your `tsconfig.json`.