From 019b4146a364f44ebc724cfe08e963034c100457 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?N=C3=ADcholas=20Andr=C3=A9?= Date: Mon, 3 Jun 2024 15:50:42 -0300 Subject: [PATCH] Update _includes/markdown/Typescript.md Co-authored-by: Antonio Laguna --- _includes/markdown/Typescript.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_includes/markdown/Typescript.md b/_includes/markdown/Typescript.md index f8598f09..58fea4a9 100644 --- a/_includes/markdown/Typescript.md +++ b/_includes/markdown/Typescript.md @@ -16,7 +16,7 @@ We also recognize that the industry has largely adopted TypeScript as the de fac At 10up we require that all projects considered "JavaScript-First" to make use of TypeScript. Generally speaking Standard WordPress projects (including block development) would not fall under "JavaScript-First" projects. -If you are building a project using Next.js and/or 10up's [HeadstartWP framework](https://headstartwp.10up.com/), Sanity and any other headless CMS'es powered by a React front-end then we require TypeScript unless other circumstances make using JavaScript a better choice. +If you are building a project using Next.js and/or 10up's [HeadstartWP framework](https://headstartwp.10up.com/), Sanity and any other headless CMSs' powered by a React front-end then we require TypeScript unless other circumstances make using JavaScript a better choice. The main reason we don't require TypeScript for standard WordPress projects is that TypeScript support for block development is still very limited, largely driven by community types packages that don't always match the actual types for the `@wordpress` packages.