bump

Author: ssalbdivad

ark/docs/public/llms.txt

@@ -354,7 +354,13 @@ title: Announcing arkregex
 description: A drop-in replacement for new RegExp() with types
 ---
 
-The `regex` function creates a `Regex` instance with types for `.test()`, `.exec()` and more, statically parsed from native JS syntax.
+Regular expressions are ubiquitous in modern code.
+
+A few characters sprinkled into your JavaScript can validate and parse strings that would require dozens of lines of imperative logic.
+
+However, that concision comes at a cost. Complex expressions can be hard to understand and type safety is a pipe dream- or at least, it was.
+
+Introducing `arkregex`, a type-safe wrapper of `new RegExp()`. The `regex` function creates a `Regex` instance with types for `.test()`, `.exec()` and more, statically parsed from native JS syntax.
 
 ```ts
 import { regex } from "arkregex"
@@ -369,22 +375,22 @@ const email = regex("^(?<name>\\w+)@(?<domain>\\w+\\.\\w+)$")
 // 	  ^ Regex<`${string}@${string}.${string}`, { names: { name: string; domain: `${string}.${string}`; }; ...>
 ```
 
-## Features
+### Features
 
 - **Types**: Infers string types for your existing regular expressions, including positional and named captures
 - **Parity**: Supports 100% of [features](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_expressions) allowed by `new RegExp()`
 - **Safety**: Syntax errors like referencing a group that doesn't exist are now type errors
-- **Zero Runtime**: Improves your type safety without impacting your bundle size[\*](#footnote)
+- **Zero Runtime**: Improves your type safety without impacting your bundle size
 
-## FAQ
+### FAQ
 
-### Why aren't some patterns like `[a-Z]` inferred more precisely?
+#### Why aren't some patterns like `[a-Z]` inferred more precisely?
 
 Constructing string literal types for these sorts of expressions is combinatorial and will explode very quickly if we infer character ranges like this as literal characters.
 
 We've tried to strike a balance between performance and precision while guaranteeing that the inferred types are at worst imprecise and never incorrect.
 
-### Why doesn't it work with my massive RegExp?
+#### Why doesn't it work with my massive RegExp?
 
 If your expression is especially long or complex, TypeScript won't be able to infer it.
 
@@ -396,14 +402,6 @@ const complexPattern = regex.cast<`pattern-${string}`, { captures: [string] }>(
 )
 ```
 
-<a id="footnote"></a>
-\*The actual runtime bundle size is two lines:
-
-```js
-export const regex = (src, flags) => new RegExp(src, flags)
-Object.assign(regex, { cast: regex })
-```
-
 <MainAutoplayDemo />
 
 ⚡ [Starting coding](/docs/intro/setup)