Types from `tailwindcss/types/config` are not available in v4

[kachkaev]

What version of Tailwind CSS are you using?

v4.0.3

What build tool (or framework if it abstracts the build tool) are you using?

typescript 5.7.3, any framework

What version of Node.js are you using?

v22.13.1

What browser are you using?

N/A

What operating system are you using?

N/A

Reproduction URL

kachkaev/tailwind-v4-typings#1

↑ See tsc failure in CI (it passes on main for TailwindCSS v3)

Describe your issue

I am trying to upgrade a project from TailwindCSS v3 to v4. There is a custom tailwind.config.ts which is quite hard to migrate to a CSS file, at least in one go. I would like to keep using tailwind.config.ts but have trouble with this because of typings. This import path is no longer available:

import type { PluginAPI, ThemeConfig } from "tailwindcss/types/config";

I understand that CSS config is preferred over the TS one, just looking for a practical way to upgrade. It’d be great to keep tailwindcss/types/config (or alike) available in v4. Typings can be removed in v5 if there is a plan to drop TS configs completely.

[SantaClaas]

I would like to add to this that it makes migrating plugins to v4 harder too.
If I am not missing something then it seems like the types are defined in the package but not exported and can only be accessed through other exposed types like the plugin function e.g.

import plugin from "tailwindcss/plugin";
type ThemeConfig = Required<Required<Parameters<typeof plugin>>[1]>["theme"];

But that is not very ergonomic.

[philipp-spiess]

Hey! We added these type exports to the tailwindcss/plugin export, so this should work with the next patch release:

import type {Cofig, PluginAPI, PluginCreator, PluginsConfig, ThemeConfig } from 'tailwindcss/plugin'

Thank you for reporting!