Add docs

Author: philipp-spiess

packages/@tailwindcss-vite/README.md

@@ -21,10 +21,43 @@
 
 ---
 
+# `@tailwindcss/vite`
+
 ## Documentation
 
 For full documentation, visit [tailwindcss.com](https://tailwindcss.com).
 
+---
+
+## Advanced topics
+
+### API reference
+
+The Vite plugin can be configured by passing an object to the `tailwindcss()`. Here is a full list of available options:
+
+| Property                                      | Values                                    |
+| --------------------------------------------- | ----------------------------------------- |
+| [`scanner`](#disabling-module-graph-scanning) | `module-graph` _(default)_, `file-system` |
+
+### Disabling module-graph scanning
+
+Our Vite plugin is designed to take the Vite module graph into account when scanning for utilities used in your project. This will work well in most cases since the module graph contains all markup that will be in your final build.
+
+However, sometimes your Vite setup is split across different build steps (e.g. when using SSR builds). If that is the case, you might find that the client build might contain more utilities since it traverses all components while the server build doesn't.
+
+To ensure that both builds read all components from your project, set the `scanner` option to `file-system`:
+
+```js
+import { defineConfig } from 'vite'
+import tailwindcss from '@tailwindcss/vite'
+
+export default defineConfig({
+  plugins: [tailwindcss({ scanner: 'file-system' })],
+})
+```
+
+---
+
 ## Community
 
 For help, discussion about best practices, or any other conversation that would benefit from being searchable: