chore: update astro docs deps and add deprecation badges

docs/src/components/Head.astro

@@ -2,7 +2,8 @@
 import Default from '@astrojs/starlight/components/Head.astro';
 import type { Props } from '@astrojs/starlight/props';
 ---
+
 <Default {...Astro.props}>
   <slot />
 </Default>
-<script src="../setup"></script>
+<script src="../setup"></script>

docs/src/content/docs/reference/Utils/tokens.md → docs/src/content/docs/reference/Utils/tokens.mdx

@@ -2,13 +2,13 @@
 title: Tokens
 ---
 
+import { Badge } from '@astrojs/starlight/components';
+
 These utilities have to do with processing/formatting tokens.
 
-## flattenTokens
+## flattenTokens <Badge text="Deprecated" variant="danger" />
 
-:::caution
-Deprecated in favor of [`convertTokenData`](/reference/utils/tokens#converttokendata), see below
-:::
+> Deprecated in favor of [`convertTokenData`](/reference/utils/tokens#converttokendata), see below.
 
 Flatten dictionary tokens object to an array of flattened tokens.
 

docs/src/content/docs/reference/api.md → docs/src/content/docs/reference/api.mdx

@@ -4,6 +4,8 @@ sidebar:
   order: 1
 ---
 
+import { Badge } from '@astrojs/starlight/components';
+
 ## new StyleDictionary()
 
 Create a new StyleDictionary instance.
@@ -204,7 +206,7 @@ type formatPlatform = (
 | platform | `string`              | Name of the platform you want to build.                                                                                                                         |
 | opts     | `{ cache?: boolean }` | `cache` prop determines whether or not it should reuse the cached tokens/config if they've already been processed earlier for this platform. `false` by default |
 
-Runs [`getPlatform`](#getplatform) under the hood, and then loops over the `files`, and formats the dictionary for each file, returning an array of file objects:
+Runs [`getPlatformTokens`](#getplatformtokens) under the hood, and then loops over the `files`, and formats the dictionary for each file, returning an array of file objects:
 
 - `output` property, which is usually a string but depending on the format, it could also be any other data type. This is useful if you don't intend to write to a file, but want to do something else with the formatted tokens.
 - `destination` property, this one is optional, if you don't intend on writing to a file you don't need this, but it can still be useful to name your outputs if you've got multiple `files`.
@@ -337,7 +339,9 @@ defined in the platform and calls the undo method on any actions.
 - For `exportPlatform`, use `getPlatformTokens` instead, turning off the cache option if needed.
 - For `getPlatform`, use `getPlatformConfig` insetad, turning off the cache option if needed.
 
-### exportPlatform
+### exportPlatform <Badge text="Deprecated" variant="danger" />
+
+> Deprecated in favor of [`getPlatformTokens`](#getplatformtokens).
 
 ```ts
 type exportPlatform = (platform: string, opts: { cache?: boolean }) => Promise<DesignTokens>;
@@ -354,7 +358,9 @@ This is useful if you want to use a Style Dictionary in JS build tools like Webp
 
 ---
 
-### getPlatform
+### getPlatform <Badge text="Deprecated" variant="danger" />
+
+> Deprecated in favor of [`getPlatformConfig`](#getplatformconfig).
 
 ```ts
 type getPlatform = (

lib/fs.js

@@ -1,3 +1,4 @@
+// @ts-expect-error missing default export in type d file, but present in ESM entrypoint
 import memfs from '@bundled-es-modules/memfs';
 
 /**