Upgrade: Allow corePlugins in JS config files

tailwindlabs · Oct 21, 2024 · 5f89040 · 5f89040
1 parent 1c5bb39
commit 5f89040
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -10,6 +10,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Added
 
 - _Upgrade (experimental)_: Migrate `plugins` with options to CSS ([#14700](https://github.com/tailwindlabs/tailwindcss/pull/14700))
+- _Upgrade (experimental)_: Allow JS configuration files with `corePlugins` options to be migrated to CSS ([#14742](https://github.com/tailwindlabs/tailwindcss/pull/14742))
 
 ### Fixed
 

diff --git a/packages/@tailwindcss-upgrade/src/migrate-js-config.ts b/packages/@tailwindcss-upgrade/src/migrate-js-config.ts
@@ -63,6 +63,12 @@ export async function migrateJsConfig(
     if (themeConfig) cssConfigs.push(themeConfig)
   }
 
+  if ('corePlugins' in unresolvedConfig) {
+    info(
+      `Your configuration file contains a \`corePlugins\` property, which is no longer available in Tailwind CSS v4. This option was not migrated to CSS.`,
+    )
+  }
+
   let simplePlugins = findStaticPlugins(source)
   if (simplePlugins !== null) {
     for (let [path, options] of simplePlugins) {
@@ -214,6 +220,7 @@ function canMigrateConfig(unresolvedConfig: Config, source: string): boolean {
     'plugins',
     'presets',
     'prefix', // Prefix is handled in the dedicated prefix migrator
+    'corePlugins',
   ]
 
   if (Object.keys(unresolvedConfig).some((key) => !knownProperties.includes(key))) {