Fix: spelling of "TypeScript"

facebook · Dec 6, 2023 · 6dcddf6 · 6dcddf6
1 parent ab9028d
commit 6dcddf6
Show file tree

Hide file tree

Showing 11 changed files with 23 additions and 23 deletions.
diff --git a/apps/docs/blog/2023-12-05-introducing-stylex.md b/apps/docs/blog/2023-12-05-introducing-stylex.md
@@ -74,7 +74,7 @@ always merge with predictable results.
 
 ### Type-Safe
 
-You can constrain the styles a component accepts by using Typescript or Flow
+You can constrain the styles a component accepts by using TypeScript or Flow
 types. Every style property and variable is fully typed.
 
 ### Colocation

diff --git a/apps/docs/docs/api/types/StaticStyles.mdx b/apps/docs/docs/api/types/StaticStyles.mdx
@@ -40,10 +40,10 @@ Any key not defined in the object type will be disallowed.
 
 :::danger Only known keys are checked
 
-Due to a Typescript limitation, any key not in your custom object type
+Due to a TypeScript limitation, any key not in your custom object type
 will only be disallowed if it's one of the known style properties
 in the internal StyleX types.
 
-Typescript will not error if you pass an additional unknown key.
+TypeScript will not error if you pass an additional unknown key.
 
 :::
diff --git a/apps/docs/docs/api/types/StyleXStyles.mdx b/apps/docs/docs/api/types/StyleXStyles.mdx
@@ -38,10 +38,10 @@ Any key not defined in the object type will be disallowed.
 
 :::danger Only known keys are checked
 
-Due to a Typescript limitation, any key not in your custom object type
+Due to a TypeScript limitation, any key not in your custom object type
 will only be disallowed if it's one of the known style properties
 in the internal StyleX types.
 
-Typescript will not error if you pass an additional unknown key.
+TypeScript will not error if you pass an additional unknown key.
 
-:::
+:::
diff --git a/apps/docs/docs/learn/02-thinking-in-stylex.mdx b/apps/docs/docs/learn/02-thinking-in-stylex.mdx
@@ -190,7 +190,7 @@ There should be no surprises.
 
 ### Type-Safe styles
 
-Typescript has become massively popular due to the experience and safety it
+TypeScript has become massively popular due to the experience and safety it
 provides. Our styles, however, have largely remained untyped and unreliable.
 Other than some path-breaking projects such as
 [Vanilla Extract](https://vanilla-extract.style/), styles are just bags of
@@ -199,7 +199,7 @@ strings in most styling solutions.
 StyleX is authored in Flow with strong static types. Its packages on NPM come
 with auto-generated types for both Flow and TypeScript. When there are
 incompatibilities between the two type-systems, we take the time to ensure that we
-write custom Typescript types to achieve at least the same level of power and safety
+write custom TypeScript types to achieve at least the same level of power and safety
 as the original Flow.
 
 _All styles are typed_. When accepting styles as props, types can be used to
@@ -254,7 +254,7 @@ a component's styles can be customized with **zero-runtime cost**.
 ### Shareable constants
 
 CSS class names, CSS variables, and other CSS identifiers are defined in a global
-namespace. Bringing CSS strings into JavaScript can mean losing type-safety and 
+namespace. Bringing CSS strings into JavaScript can mean losing type-safety and
 composability.
 
 We want styles to be type-safe, so we've spent a lot of time coming up with

diff --git a/apps/docs/docs/learn/06-static-types.mdx b/apps/docs/docs/learn/06-static-types.mdx
@@ -17,7 +17,7 @@ StyleX comes with full support for Static Types. The most common utility type is
 `StyleXStyles` which is used to accept any arbitrary StyleX styles.
 
 <Tabs>
-  <TabItem value="typescript" label="Typescript" default>
+  <TabItem value="typescript" label="TypeScript" default>
 
 ```tsx
 import type {StyleXStyles} from '@stylexjs/stylex';
@@ -83,7 +83,7 @@ To limit the accepted style properties to a given set, an object type with the
 allowed properties can be used:
 
 <Tabs>
-  <TabItem value="typescript" label="Typescript" default>
+  <TabItem value="typescript" label="TypeScript" default>
 
 ```tsx
 import type {StyleXStyles} from '@stylexjs/stylex';
@@ -135,9 +135,9 @@ baseline styles in the component itself.
 
 :::
 
-:::danger Typescript may not catch extra style properties
+:::danger TypeScript may not catch extra style properties
 
-Typescript object types don’t error when given objects with extra properties.
+TypeScript object types don’t error when given objects with extra properties.
 We’ve taken steps to mitigate this issue, but there may be edge-cases where
 you’ll be able to pass in extra, disallowed styles without a type error.
 
@@ -149,7 +149,7 @@ In addition to the accepted style properties, the values for those properties
 can be constrained too.
 
 <Tabs>
-  <TabItem value="typescript" label="Typescript" default>
+  <TabItem value="typescript" label="TypeScript" default>
 
 ```tsx
 import type {StyleXStyles} from '@stylexjs/stylex';
@@ -192,7 +192,7 @@ other properties. The value for `marginTop` can only be one of `0`, `4`, `8`, or
 It is sometimes more convenient to define a blocklist instead of an allowlist.
 
 <Tabs>
-  <TabItem value="typescript" label="Typescript" default>
+  <TabItem value="typescript" label="TypeScript" default>
 
 ```tsx
 import type {StyleXStylesWithout} from '@stylexjs/stylex';

diff --git a/apps/nextjs-example/typetests/typetests.ts b/apps/nextjs-example/typetests/typetests.ts
@@ -197,7 +197,7 @@ const styles6: Readonly<{
           '@media (max-width: 1000px)': mobile,
         },
       },
-    }) as const, // Typescript limitation
+    }) as const, // TypeScript limitation
 });
 // @ts-expect-error - Functions don't return static styles.
 styles6.foo(100) satisfies StaticStyles;

diff --git a/packages/babel-plugin/README.md b/packages/babel-plugin/README.md
@@ -12,7 +12,7 @@ by passing them to the functions of the corresponding names within `@stylex/shar
 
 ## Babel Metadata
 
-The StyleX Babel plugin does more than transform JavaScript (or Typescript) files. It also returns a list of injected styles. The way that such a value can be returned while transforming a JS file is by using Babel's `metadata` API.
+The StyleX Babel plugin does more than transform JavaScript (or TypeScript) files. It also returns a list of injected styles. The way that such a value can be returned while transforming a JS file is by using Babel's `metadata` API.
 
 An example of this can be seen in some of the tests, but the result of using Babel's `transform(...)` function returns an object contains at least two keys:
 

diff --git a/packages/nextjs-plugin/src/custom-webpack-plugin.js b/packages/nextjs-plugin/src/custom-webpack-plugin.js
@@ -97,7 +97,7 @@ class StylexPlugin {
           if (
             // JavaScript (and Flow) modules
             /\.jsx?/.test(path.extname(module.resource)) ||
-            // Typescript modules
+            // TypeScript modules
             /\.tsx?/.test(path.extname(module.resource))
           ) {
             // We use .push() here instead of .unshift()
@@ -194,7 +194,7 @@ class StylexPlugin {
         {
           babelrc: this.babelConfig.babelrc,
           filename,
-          // Use Typescript syntax plugin if the filename ends with `.ts` or `.tsx`
+          // Use TypeScript syntax plugin if the filename ends with `.ts` or `.tsx`
           // and use the Flow syntax plugin otherwise.
           plugins: [
             ...this.babelConfig.plugins,

diff --git a/packages/scripts/gen-types.js b/packages/scripts/gen-types.js
@@ -104,7 +104,7 @@ async function generateTypes(inputDir, outputDir, rootDir) {
 
           await fsPromises.writeFile(
             outputFullPath.replace(/\.js$/, '.d.ts'),
-            // Typescript Prefers `NodePath` unlike `NodePath<>` in Flow
+            // TypeScript Prefers `NodePath` unlike `NodePath<>` in Flow
             // `flow-api-translator` doesn't handle this case yet.
             postProcessTSOutput(outputTSContents),
           );

diff --git a/packages/stylex/src/StyleXCSSTypes.js b/packages/stylex/src/StyleXCSSTypes.js
@@ -868,7 +868,7 @@ export type CSSProperties = $ReadOnly<{
   // NOTE: adding a non-CSS property here for support themes in Stylex.
   theme?: all | string,
 
-  // ...$Exact<SupportedVendorSpecificCSSProperties>, for Typescript compatibility
+  // ...$Exact<SupportedVendorSpecificCSSProperties>, for TypeScript compatibility
   MozOsxFontSmoothing?: all | 'grayscale',
   WebkitAppearance?: all | appearance,
   WebkitFontSmoothing?: all | 'antialiased',

diff --git a/packages/webpack-plugin/src/index.js b/packages/webpack-plugin/src/index.js
@@ -73,7 +73,7 @@ class StylexPlugin {
           if (
             // JavaScript (and Flow) modules
             /\.jsx?/.test(path.extname(module.resource)) ||
-            // Typescript modules
+            // TypeScript modules
             /\.tsx?/.test(path.extname(module.resource))
           ) {
             // It might make sense to use .push() here instead of .unshift()
@@ -165,7 +165,7 @@ class StylexPlugin {
         {
           babelrc: this.babelConfig.babelrc,
           filename,
-          // Use Typescript syntax plugin if the filename ends with `.ts` or `.tsx`
+          // Use TypeScript syntax plugin if the filename ends with `.ts` or `.tsx`
           // and use the Flow syntax plugin otherwise.
           plugins: [
             ...this.babelConfig.plugins,