tailwindcss/packages
Jordan Pittman 783b32305f
Export Config type (#14360)
Right now the following does not work and instead produces a type error:

```
import { type Config } from 'tailwindcss'

export default {
  // … config here
} satisfies Config
```

We were not exporting a `Config` type but thankfully this already exists
in the codebase so we just need to export it.

It does _not_ have all properties of an existing config as not all
features have been implemented (or in some cases necessary / relevant
for v4).

Notably missing are:
- `important`
- `prefix`
- `separator`
- `safelist`
- `blocklist`
- `future`
- `experimental`
- `corePlugins`

Also, explicit keys for theme are not currently specified but we should
probably bring this back even if just as an auto-complete aid.
2024-09-06 16:10:18 -04:00
..
@tailwindcss-cli Improve the CLI output when nothing changed (#14351) 2024-09-05 17:00:57 -04:00
@tailwindcss-node v4.0.0-alpha.23 2024-09-05 10:43:07 -04:00
@tailwindcss-postcss v4.0.0-alpha.23 2024-09-05 10:43:07 -04:00
@tailwindcss-standalone v4.0.0-alpha.23 2024-09-05 10:43:07 -04:00
@tailwindcss-vite v4.0.0-alpha.23 2024-09-05 10:43:07 -04:00
internal-example-plugin Prefix internal modules with internal-* (#14074) 2024-07-29 10:58:07 -04:00
internal-postcss-fix-relative-paths Support loading config files via @config (#14239) 2024-09-02 18:03:16 +02:00
tailwindcss Export Config type (#14360) 2024-09-06 16:10:18 -04:00
tsconfig.base.json introduce v4 codebase 2024-03-05 14:29:15 +01:00