Files
20067f05bc chore: Switch Geist font imports to npm geist package (#12952)
## Summary

Switches all `Geist` / `Geist_Mono` imports from `next/font/google` to
the npm [`geist`](https://www.npmjs.com/package/geist) package (which
self-hosts via `next/font/local`).

## Why

Google Fonts serves a stripped Geist build that omits OpenType tables —
most relevantly, **Stylistic Set 11 (`ss11`)**, where Geist Mono 1.7.0
(Feb 2026) moved coding ligatures (`==>`, `->`, etc.). A fix has been
submitted to Google Fonts to ship the full Geist OpenType tables
(including ss11); we're waiting on their release. Once it lands, this PR
can be reverted and we can go back to next/font/google.

| **Before**  | **After** |
| ------------- | ------------- |
| <img width="850" alt="image"
src="https://github.com/user-attachments/assets/80c4fe43-71aa-41a6-b0d1-0bd012c86b96"
/> | <img width="850" alt="image"
src="https://github.com/user-attachments/assets/6b47a3ec-93a1-46c9-8c00-cb166bcbcfe1"
/> |

## Changes

- Switched imports in:
  - `examples/with-nextjs-elysia/apps/web/src/app/layout.tsx`
  - `examples/with-tailwind/apps/{web,docs}/app/layout.tsx`
  - `examples/non-monorepo/app/layout.tsx`
- `apps/docs/lib/geistdocs/fonts.ts` (re-exports `GeistSans`/`GeistMono`
as `sans`/`mono` to keep call sites unchanged)
- The npm `geist` package hardcodes `--font-geist-sans` /
`--font-geist-mono`, so renamed `var(--font-mono, …)` →
`var(--font-geist-mono, …)` in:
  - `apps/docs/components/diagram/sequence-diagram.tsx`
  - `apps/docs/components/diagram/flow-diagram.tsx`
- Added `"geist": "^1.7.1"` to the five affected `package.json` files.

---------

Co-authored-by: Hanzo Dev <[email protected]>
2026-05-26 15:01:06 -06:00
..

Getting Started

First, run the development server:

yarn dev

Open http://localhost:3001 with your browser to see the result.

You can start editing the page by modifying src/app/page.tsx. The page auto-updates as you edit the file.

To create API routes add an api/ directory to the app/ directory with a route.ts file. For individual endpoints, create a subfolder in the api directory, like api/hello/route.ts would map to http://localhost:3001/api/hello.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.