Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Experimental support for custom Tailwind configurations (#340)
This PR adds a `tailwindConfig` option to pass a custom configuration down to `twrnc`, which allows sharing tokens between front-end and OG images in a single codebase already using Tailwind. <img width="1728" alt="Custom Tailwind classes used in Satori's playground" src="https://user-images.githubusercontent.com/6959425/208383229-03e9329c-a50f-47b3-9edb-7b8dc9c56b9c.png"> #### Tests I wasn't sure if I should add tests given that Tailwind support is labeled `experimental` and that there are no Tailwind-related tests currently. #### `@vercel/og` What's the process like to surface new `satori` features up to `@vercel/og`? (e.g. adding a `tailwindConfig` option there too) --------- Co-authored-by: Shu Ding <[email protected]>
- Loading branch information
bc615fa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully deployed to the following URLs:
satori-playground – ./
og-playground.vercel.sh
satori-playground.vercel.app
satori-playground.vercel.sh
satori-playground-git-main.vercel.sh
og-playground.vercel.app