TypeError: getProcessedPlugins is not a function #2810

GregSitholeEntrostat · 2020-11-19T08:13:37Z

Describe the problem:

Upgraded from TailwindCSS 1.9.6 to 2.0.1 for my angular project following the instructions on their website. I had previously used the following guide: https://notiz.dev/blog/angular-10-with-tailwindcss#setup to Install the previous version and that worked before.

Please see error below:

ERROR in Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
TypeError: getProcessedPlugins is not a function
    at /home/greg/angular-website/frontend/node_modules/tailwindcss/lib/processTailwindFeatures.js:71:83
    at LazyResult.runOnRoot (/home/greg/angular-website/frontend/node_modules/postcss/lib/lazy-result.js:276:16)
    at LazyResult.runAsync (/home/greg/angular-website/frontend/node_modules/postcss/lib/lazy-result.js:328:26)
    at async Object.loader (/home/greg/angular-website/frontend/node_modules/postcss-loader/dist/index.js:94:14)

ERROR in ./src/styles.scss (./node_modules/css-loader/dist/cjs.js??ref--13-1!./node_modules/@angular-devkit/build-angular/node_modules/postcss-loader/src??embedded!./node_modules/resolve-url-loader??ref--13-3!./node_modules/sass-loader/dist/cjs.js??ref--13-4!./node_modules/postcss-loader/dist/cjs.js??ref--17!./src/styles.scss)
Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
TypeError: getProcessedPlugins is not a function
    at /home/greg/angular-website/frontend/node_modules/tailwindcss/lib/processTailwindFeatures.js:71:83
    at LazyResult.runOnRoot (/home/greg/angular-website/frontend/node_modules/postcss/lib/lazy-result.js:276:16)
    at LazyResult.runAsync (/home/greg/angular-website/frontend/node_modules/postcss/lib/lazy-result.js:328:26)
    at async Object.loader (/home/greg/angular-website/frontend/node_modules/postcss-loader/dist/index.js:94:14)

The text was updated successfully, but these errors were encountered:

alexcroox · 2020-11-19T09:09:53Z

I too am getting this, I'm using the PostCSS 7 compatibility build with Vue 2

"postcss": "^7.0.35",
"tailwindcss": "^2.0.1-compat"

For anyone coming from Google, you need to make sure you have upgraded to Node.js 12.13 or higher for Tailwind v2

GregSitholeEntrostat · 2020-11-19T09:53:00Z

@alexcroox I managed to fix it on my end.

What I did was I removed the existing tailwind.config.js and just ran the command npx tailwindcss init --full, then I just applied the custom configurations that I did to it. I'm going to close the issue since I fixed my original issue

SimonPrague · 2020-11-19T10:02:08Z

I have the same issue and was not able to resolve it yet.
Can it be due to the use of plugins?

  plugins: [
    require('@tailwindcss/ui'),
    require('@tailwindcss/forms'),
    require('@tailwindcss/typography'),
  ],

alexcroox · 2020-11-19T10:04:42Z

@GregSitholeEntrostat what was the diff on your tailwind.config.js? Perhaps there is something missing in the upgrade guide?

Could you re-open as it seems others are hitting this issue and we've not got to the cause yet.

GregSitholeEntrostat · 2020-11-19T10:11:11Z

@alexcroox There's quite a bit of change. Here's a link to their latest version https://github.com/tailwindlabs/tailwindcss/blob/master/stubs/defaultConfig.stub.js

@SimonPrague I'm not too sure, I'm not familiar with those plugins and currently not using any! Have you tried to see what happens when you remove the plugins?

SimonPrague · 2020-11-19T10:13:55Z

It breaks the same even with removing those plugins :(

SimonPrague · 2020-11-19T10:26:17Z

Ok I removed the UI plugin as it seems no longer required for TailwindUI. But I get this error instead:

error  in ./src/components/profile/widgets/***.vue?vue&type=style&index=0&id=71d401a6&scoped=true&lang=postcss

Module build failed (from ./node_modules/.pnpm/[email protected]/node_modules/postcss-loader/src/index.js):
TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at Object.module.exports [as typography] (/home/***/client/node_modules/.pnpm/@tailwindcss/[email protected][email protected]/node_modules/@tailwindcss/typography/src/styles.js:1076:13)
    at /home/***/client/node_modules/.pnpm/[email protected]_01b244ddc5034529ac96d3fe28ec275b/node_modules/tailwindcss/lib/util/resolveConfig.js:135:65
    at Array.reduce (<anonymous>)
    at resolveFunctionKeys (/home/***/client/node_modules/.pnpm/[email protected]_01b244ddc5034529ac96d3fe28ec275b/node_modules/tailwindcss/lib/util/resolveConfig.js:133:30)
    at resolveConfig (/home/***/client/node_modules/.pnpm/[email protected]_01b244ddc5034529ac96d3fe28ec275b/node_modules/tailwindcss/lib/util/resolveConfig.js:270:12)
    at /home/***/client/node_modules/.pnpm/[email protected]_01b244ddc5034529ac96d3fe28ec275b/node_modules/tailwindcss/lib/index.js:75:37
    at /home/***/client/node_modules/.pnpm/[email protected]_01b244ddc5034529ac96d3fe28ec275b/node_modules/tailwindcss/lib/processTailwindFeatures.js:50:20
    at LazyResult.run (/home/***/client/node_modules/.pnpm/[email protected]/node_modules/postcss/lib/lazy-result.js:288:14)
    at LazyResult.asyncTick (/home/***/client/node_modules/.pnpm/[email protected]/node_modules/postcss/lib/lazy-result.js:212:26)
    at LazyResult.asyncTick (/home/***/client/node_modules/.pnpm/[email protected]/node_modules/postcss/lib/lazy-result.js:225:14)
    at /home/***/client/node_modules/.pnpm/[email protected]/node_modules/postcss/lib/lazy-result.js:254:14
    at new Promise (<anonymous>)
    at LazyResult.async (/home/***/client/node_modules/.pnpm/[email protected]/node_modules/postcss/lib/lazy-result.js:250:23)
    at LazyResult.then (/home/***/client/node_modules/.pnpm/[email protected]/node_modules/postcss/lib/lazy-result.js:131:17)
    at /home/***/client/node_modules/.pnpm/[email protected]/node_modules/postcss-loader/src/index.js:142:8

SimonPrague · 2020-11-19T10:27:36Z

I guess that could be related to #861

creimers · 2020-11-19T10:46:26Z

I managed solving the problem like so: https://tailwindcss.com/docs/installation#post-css-7-compatibility-build

SimonPrague · 2020-11-19T10:51:15Z

That did not help. Is it possible due to the change in colors? I was using both gray and cool-gray and it seems there were some changes...

SimonPrague · 2020-11-19T11:01:22Z

Ok I've added alias for cool-gray and I'm back to the TypeError: getProcessedPlugins is not a function and even with the compat build :(

SimonPrague · 2020-11-19T11:16:39Z

OK I have no solution so far. It might be because of: vue cli and postcss loader
vuejs/vue-cli#6064

SimonPrague · 2020-11-19T11:38:28Z

Anyone got Tailwind 2 working with Typescript & Vue Cli & Vue 3, heh?

lesteak · 2020-11-19T12:18:28Z

I also had this issue. did you follow the upgrade guide?

Specifically, did you upgrade postcss?
npm install tailwindcss@latest postcss@latest autoprefixer@latest

SimonPrague · 2020-11-19T14:56:13Z

Yep, I followed these instructions. I tried both latest and comp versions. Still the same problem.

IgorNoskov · 2020-11-19T14:59:08Z

Hey guys! I have the same problem. I've been trying to migrate to tailwind 2 for hours now.

IgorNoskov · 2020-11-19T15:03:16Z

Whatever I do, I get a TypeError: getProcessedPlugins is not a function.

CreateSean · 2020-11-19T16:47:19Z

What I did was I removed the existing tailwind.config.js and just ran the command npx tailwindcss init --full, then I just applied the custom configurations that I did to it. I'm going to close the issue since I fixed my original issue

I tried that but still get errors

Module build failed (from ./node_modules/css-loader/index.js):
ModuleBuildError: Module build failed (from ./node_modules/postcss-loader/src/index.js):
TypeError: getProcessedPlugins is not a function
    at D:\sites\Land-Development\node_modules\tailwindcss\lib\processTailwindFeatures.js:71:83
    at LazyResult.run (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:288:14)
    at LazyResult.asyncTick (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:212:26)
    at LazyResult.asyncTick (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:225:14)
    at D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:254:14
    at new Promise (<anonymous>)
    at LazyResult.async (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:250:23)
    at LazyResult.then (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:131:17)
    at Promise.resolve.then.then (D:\sites\Land-Development\node_modules\postcss-loader\src\index.js:142:8)
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at runLoaders (D:\sites\Land-Development\node_modules\webpack\lib\NormalModule.js:316:20)
    at D:\sites\Land-Development\node_modules\loader-runner\lib\LoaderRunner.js:367:11
    at D:\sites\Land-Development\node_modules\loader-runner\lib\LoaderRunner.js:233:18
    at context.callback (D:\sites\Land-Development\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
    at Promise.resolve.then.then.catch (D:\sites\Land-Development\node_modules\postcss-loader\src\index.js:208:9)
    at process._tickCallback (internal/process/next_tick.js:68:7)
 @ ./src/css/app.css

ERROR in ./src/css/app.css (./node_modules/css-loader??ref--8-2!./node_modules/postcss-loader/src??postcss0!./src/css/app.css)
Module build failed (from ./node_modules/postcss-loader/src/index.js):    
TypeError: Object.entries(...).flatMap is not a function
    at flattenColorPalette (D:\sites\Land-Development\node_modules\tailwindcss\lib\util\flattenColorPalette.js:8:83)
    at D:\sites\Land-Development\node_modules\tailwindcss\lib\plugins\divideColor.js:27:53
    at plugins.forEach.plugin (D:\sites\Land-Development\node_modules\tailwindcss\lib\util\processPlugins.js:69:5)
    at Array.forEach (<anonymous>)
    at _default (D:\sites\Land-Development\node_modules\tailwindcss\lib\util\processPlugins.js:63:11)
    at D:\sites\Land-Development\node_modules\tailwindcss\lib\processTailwindFeatures.js:60:54
    at LazyResult.run (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:288:14)
    at LazyResult.asyncTick (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:212:26)
    at LazyResult.asyncTick (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:225:14)
    at D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:254:14
    at new Promise (<anonymous>)
    at LazyResult.async (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:250:23)
    at LazyResult.then (D:\sites\Land-Development\node_modules\postcss\lib\lazy-result.js:131:17)
    at Promise.resolve.then.then (D:\sites\Land-Development\node_modules\postcss-loader\src\index.js:142:8)
 @ ./src/css/app.css 2:14-142```

ThreeScreenStudios · 2020-11-19T17:09:42Z

I was able to get Tailwind 2 and Vue 2 w/ Cli to work with the compatibility build - currently I believe Vue Cli uses an old version of postcss-loader and thus does not support postcss 8. Hopefully they'll update it in the future (added a request here).

Steps I took:

Remove tailwind npm package, install tailwindcss@compat
Removed require('@tailwindcss/ui') from plugins in tailwind.config.js, add require('@tailwindcss/forms') (there will be styling changes needed, like type="text" required for all plain text inputs)
Check to see if any other plugins require postcss 8 (latest postcss-nested does for example), roll back those packages to an earlier version
Updated custom color theme in tailwind.config.js (syntax changed a bit, see here), also need to add in things like white and transparent if you used those.
Run yarn/npm run serve, fix any styling compat errors, should hopefully run after that!

audn · 2020-11-19T17:10:55Z

Hmm.. I had the same error, but fixed it by just fooling around. Try to copy my settings?

This is a pretty big deal too, read the thingy: https://tailwindcss.com/docs/upgrading-to-v1#1-update-tailwind

let colors = require('tailwindcss/colors');

module.exports = {
  theme: {
    inset: {
      '1/2': '50%',
      '-5': '-5px',
      '-10': '-10px',
      '-15': '-15px',
      '-55': '-55%;',
      '-8': '-32px',
      114: '114px',
      96: '96px',
      0: 0,
      90: '90px',
      80: '80px',
    },
    extend: {
      margin: {
        none: 'initial',
        26: '7rem',
      },
      maxWidth: {
        card: '410px',
      },
      minWidth: {
        card: '344px',
      },
      height: {
        card: '200px',
        priceContent: '234px',
      },
      width: {
        pricing: '335px',
        245: '245px',
        280: '280px',
        345: '345px',
        hr: '200px',
      },
      colors,
      fontFamily: {
        sans: ['proxima-soft', 'sans-serif'],
      },
    },
  },
  variants: {
    textColor: ['responsive', 'hover', 'focus', 'group-hover'],
    textDecoration: ['group-hover'],
    minWidth: ['responsive'],
    opacity: ['group-hover'],
    backgroundColor: ['responsive', 'hover', 'focus', 'group-hover'],
    backgroundOpacity: ['responsive', 'hover', 'focus'],
  },
  plugins: [
    // ...
  ],
};

adamwathan · 2020-11-19T17:57:41Z

Can someone publish a GitHub repo that reproduces the issue? I suspect it will be fixed by switching to the new compatibility build:

npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9

The issue we have been seeing is that npm install tailwindcss@compat installs ^2.0.1-compat which also matches 2.0.1 which was causing the wrong version to be installed in some situations.

More details here: https://tailwindcss.com/docs/installation#post-css-7-compatibility-build

CreateSean · 2020-11-19T18:33:42Z

@adamwathan I did run the compatibility build you linked to and still get errors.

LawJolla · 2020-11-19T19:24:22Z

I don't know if this is related...

I'm running NextJS I had similar issues for hours (getProcessedPlugins and tailwindcss/plugins). Following some advice in this thread, I started from a clean config which compiled. I started incrementally adding my config back until I ended up with my old config. But it now works / compiles.

It sounds like something is cached somewhere.

seankndy · 2020-11-19T19:51:12Z

@LawJolla when you say you started from a clean config, are you referring to just the tailwind.config.js or did you do other things to start fresh?

seankndy · 2020-11-19T20:17:47Z

I setup a fresh new project and installed my css/js deps along with tailwindcss 2.0.1 and it built fine. After banging my head on it for a while I removed node_modules/tailwindcss from the project that was failing to build with getProcessedPlugins errors and copied the node_modules/tailwindcss from my other fresh project that was working and now my project is building... I understand this isn't a fix, but hoping its helpful diagnostic information for someone that understands npm much better than I.

CreateSean · 2020-11-19T21:24:16Z

I nuked my node_modules folder I also ran npm clear cache --force and tried yet again to get the compatibility build to run and it still fails.

seankndy · 2020-11-19T21:46:08Z

It appears the issue is that the tailwindcss package installed under my node_modules (./node_modules/tailwindcss/node_modules) has the postcss package installed under it at version 7.0.32. I am assuming this serves as an override to my "root" postcss package which is installed at version 8.1.8. Removing node_modules/tailwindcss/node_modules/postcss solves the problem and my project now builds.

Perhaps someone here understands why tailwindcss is including that older postcss dep into itself and how to permanently fix this? It looks to me like tailwindcss has "@fullhuman/postcss-purgecss": "^3.0.0" as a dependency and that in turn has a postcss v7 dependency which in turn overrides my global v8.

keljtanoski · 2020-11-19T21:48:15Z

Check your nodejs version (node -v) , I had v10.19.0, then made global update to v14.15.1, using vue-cli with the following dependencies
"dependencies": { "autoprefixer": "^9.8.6", "core-js": "^3.6.5", "postcss": "^7.0.35", "tailwindcss": "npm:@tailwindcss/postcss7-compat@^2.0.1", "vue": "^2.6.11", "vue-router": "^3.4.9" },

After updating node and running npm run serve I was able to build the tailwind under vue-cli

postcss.config.js
module.exports = { plugins: [ require('tailwindcss'), require('autoprefixer'), ] }

tailwind.config.js
module.exports = { purge: { content: ['./public/**/*.html', './src/**/*.vue'] }, darkMode: false, // or 'media' or 'class' theme: { extend: {}, }, variants: { extend: {}, }, plugins: [], }

carbontwelve · 2020-12-18T21:05:05Z

I know this issue is closed, however I had the same TypeError: getProcessedPlugins is not a function error crop up in my github actions but not on my local. Using npm ci followed by my build command would work on my local box but not within my github action.

I found the cause to be my local is running node v12.18.1 (npm v6.14.5) and the failing Github action was using node v10.23.0 (npm v6.14.8) updating my Github Actions config to use the same version of node as my local stopped the build from failing.

I am unsure if this is documented anywhere @adamwathan but I have seen it suggested by a few other members of the community and can confirm it was the cause of this issue in my case.

Youhan · 2020-12-28T15:01:58Z

Could be Node version too. If you use nvm like me, check if your Node is => 12

Rolando-Barbella · 2021-01-05T22:51:40Z

It works for me with node 11

liaoliaojun · 2021-01-06T07:38:19Z

Vue 3

me https://github.com/liaoliaojun/nuxt-apollo-example

jlooper · 2021-01-10T02:40:02Z

In case someone bumps into this when deploying to Netlify (just when you thought everything was perfect locally...) you can add a .node-version file to your site root and just specify 14 as the version. That makes it build and deploy ok on Netlify.

mittalvaibhav · 2021-01-26T07:48:04Z

Check your nodejs version (node -v) , I had v10.19.0, then made global update to v14.15.1, using vue-cli with the following dependencies
"dependencies": { "autoprefixer": "^9.8.6", "core-js": "^3.6.5", "postcss": "^7.0.35", "tailwindcss": "npm:@tailwindcss/postcss7-compat@^2.0.1", "vue": "^2.6.11", "vue-router": "^3.4.9" },

After updating node and running npm run serve I was able to build the tailwind under vue-cli

postcss.config.js
module.exports = { plugins: [ require('tailwindcss'), require('autoprefixer'), ] }

tailwind.config.js
module.exports = { purge: { content: ['./public/**/*.html', './src/**/*.vue'] }, darkMode: false, // or 'media' or 'class' theme: { extend: {}, }, variants: { extend: {}, }, plugins: [], }

After updating the nodejs version to v14.15.4, my issue is gone

shuzootani · 2021-01-29T13:22:42Z

in my case, updating node version to v14.7.0 from v10.22.0 fixed the error in Next.js app.
thanks to #2810 (comment)

rifandani · 2021-02-01T18:25:35Z

@SimonPrague Just spent 20 minutes recreating your project manually, the issue in your config is presets: [] in your tailwind.config.js file. You are telling Tailwind to disable the default config which causes things to blow up when you don't provide everything it's expecting manually. We can make this fail more gracefully for sure but this gets your project to build fine:
  // tailwind.config.js
  module.exports = {
    // ...
-   presets: []
    // ...
  }

This solutions works on my Next.js project! Thanks

cooskun · 2021-02-02T14:53:24Z

Updating the node to the latest version(v15.7.0) solved the problem for me!

Updating node version to solve issues on build. Ref: tailwindlabs/tailwindcss#2810

Mancancode · 2021-05-24T11:39:55Z

Hi i fixed the error "TypeError: getProcessedPlugins is not a function" by updating my Nodejs to newer version of 12.22.1
i hope this helps.

MiguelAngelParedesBustos · 2021-05-24T14:25:30Z

you need to update nvm. do nvm install {latest version}, then npm run dev and it works

darekkay · 2021-05-31T14:05:31Z

I've had the same issue, but it had nothing to do with the Node version. The issue was that I've disabled the default configuration without providing default values for enabled plugins:

module.exports = {
  presets: [],
  theme: {
    // if this line is missing, I'm getting an error
    // backgroundColor: { ... } 
  },
  corePlugins: {
    backgroundColor: true
  }
}

The error message actually points to this issue, as there are two errors:

Stack:
TypeError: Cannot convert undefined or null to object
at Function.entries ()
at flattenColorPalette (node_modules\tailwindcss\lib\util\flattenColorPalette.js:8:67)
at node_modules\tailwindcss\lib\plugins\backgroundColor.js:27:53

Stack:
TypeError: getProcessedPlugins is not a function
at node_modules\tailwindcss\lib\processTailwindFeatures.js:75:83

So the error is indeed correct, but I guess the error message could be improved.

patoncrispy · 2021-06-19T17:57:54Z

A problem I had was that I had properties under variants that should have been under variants.extend. Also, some properties were no longer valid there and had to be moved to theme.extend. Hope that helps someone else.

mpakaris · 2021-06-22T16:16:18Z

@SimonPrague Just spent 20 minutes recreating your project manually, the issue in your config is presets: [] in your tailwind.config.js file. You are telling Tailwind to disable the default config which causes things to blow up when you don't provide everything it's expecting manually. We can make this fail more gracefully for sure but this gets your project to build fine:
  // tailwind.config.js
  module.exports = {
    // ...
-   presets: []
    // ...
  }
This solutions works on my Next.js project! Thanks

This worked for me as well!

danielbachhuber · 2021-06-23T13:35:33Z

@SimonPrague Just spent 20 minutes recreating your project manually, the issue in your config is presets: [] in your tailwind.config.js file. You are telling Tailwind to disable the default config which causes things to blow up when you don't provide everything it's expecting manually. We can make this fail more gracefully for sure but this gets your project to build fine:
  // tailwind.config.js
  module.exports = {
    // ...
-   presets: []
    // ...
  }
This solutions works on my Next.js project! Thanks
This worked for me as well!

Me too! I'm glad it was an easy fix for such a cryptic error 😄

lohnsonok · 2021-07-10T15:44:25Z

@alexcroox I managed to fix it on my end.

What I did was I removed the existing tailwind.config.js and just ran the command npx tailwindcss init --full, then I just applied the custom configurations that I did to it. I'm going to close the issue since I fixed my original issue

it worked for me too ! Thank you

88brmig · 2021-07-30T02:56:53Z

@alexcroox I managed to fix it on my end.

What I did was I removed the existing tailwind.config.js and just ran the command npx tailwindcss init --full, then I just applied the custom configurations that I did to it. I'm going to close the issue since I fixed my original issue

damn king, you rock! It worked for me either.

coolcorexix · 2021-08-04T10:47:08Z

@SimonPrague Just spent 20 minutes recreating your project manually, the issue in your config is presets: [] in your tailwind.config.js file. You are telling Tailwind to disable the default config which causes things to blow up when you don't provide everything it's expecting manually. We can make this fail more gracefully for sure but this gets your project to build fine:
  // tailwind.config.js
  module.exports = {
    // ...
-   presets: []
    // ...
  }

Actually that

-   presets: []

Is included when run command npx tailwindcss init --full. And this is from the team, I supposed?
Btw the fix worked for me, thank you very much

emmaroland32 · 2021-08-11T16:08:14Z

@SimonPrague Just spent 20 minutes recreating your project manually, the issue in your config is presets: [] in your tailwind.config.js file. You are telling Tailwind to disable the default config which causes things to blow up when you don't provide everything it's expecting manually. We can make this fail more gracefully for sure but this gets your project to build fine:
  // tailwind.config.js
  module.exports = {
    // ...
-   presets: []
    // ...
  }
This solutions works on my Next.js project! Thanks

@SimonPrague Just spent 20 minutes recreating your project manually, the issue in your config is presets: [] in your tailwind.config.js file. You are telling Tailwind to disable the default config which causes things to blow up when you don't provide everything it's expecting manually. We can make this fail more gracefully for sure but this gets your project to build fine:
  // tailwind.config.js
  module.exports = {
    // ...
-   presets: []
    // ...
  }

Thanks! This worked for me with Next.js.

jakecausier · 2021-08-25T09:17:00Z

Similar to what @patoncrispy said, I had my config with the following value for variants:

variants: {
  transitionProperty: {
    'spacing': 'margin, padding'
  }
}

This was causing the root of my issues for not using extend: {} inside it, and using object notation instead of array for the properties.

tailwindlabs/tailwindcss#2810

GregSitholeEntrostat closed this as completed Nov 19, 2020

GregSitholeEntrostat reopened this Nov 19, 2020

cjkpl mentioned this issue Dec 18, 2020

npm run watch wont work cjkpl/oc-tabularasa-theme#4

Closed

liaoliaojun added a commit to liaoliaojun/nuxt-apollo-example that referenced this issue Jan 6, 2021

fix tailwind tailwindlabs/tailwindcss#2810

0772c5c

philihp mentioned this issue Jan 11, 2021

error - ./styles/index.css philihp/srmhsalumni#85

Open

bhaskarSingh mentioned this issue Jan 25, 2021

TailwindCSS setup. buidl-labs/crypto-code-school-inside-tezos#143

Merged

ezequieltejada added a commit to grupohoramasite/siteSourcev3 that referenced this issue Feb 6, 2021

Update build-deploy.yml

b019243

Updating node version to solve issues on build. Ref: tailwindlabs/tailwindcss#2810

github-jeff mentioned this issue May 17, 2021

Missing Dependency dabit3/next.js-amplify-workshop#21

Closed

hiromi-dev mentioned this issue May 26, 2021

openingの実装。 making-oasis/fly-your-message#33

Merged

cdsjuniormm mentioned this issue Jun 25, 2021

TypeError: getProcessedPlugins is not a function vuejs-br/treinamento-vue3-code#1

Open

gtyamamoto added a commit to gtyamamoto/treinamento-vue3-code that referenced this issue Aug 1, 2021

tailwind error fix tailwindlabs/tailwindcss#2810

67d74d1

applesoft1 added a commit to applesoft1/woocommerceNuxt that referenced this issue Mar 20, 2022

Fix getProcessedPlugins is not a function

3bf5544

tailwindlabs/tailwindcss#2810

TypeError: getProcessedPlugins is not a function #2810

TypeError: getProcessedPlugins is not a function #2810

Comments

GregSitholeEntrostat commented Nov 19, 2020

Describe the problem:

alexcroox commented Nov 19, 2020 • edited Loading

GregSitholeEntrostat commented Nov 19, 2020

SimonPrague commented Nov 19, 2020 • edited Loading

alexcroox commented Nov 19, 2020 • edited Loading

GregSitholeEntrostat commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

creimers commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

lesteak commented Nov 19, 2020

SimonPrague commented Nov 19, 2020

IgorNoskov commented Nov 19, 2020

IgorNoskov commented Nov 19, 2020

CreateSean commented Nov 19, 2020

ThreeScreenStudios commented Nov 19, 2020

audn commented Nov 19, 2020 • edited Loading

adamwathan commented Nov 19, 2020

CreateSean commented Nov 19, 2020

LawJolla commented Nov 19, 2020

seankndy commented Nov 19, 2020

seankndy commented Nov 19, 2020 • edited Loading

CreateSean commented Nov 19, 2020

seankndy commented Nov 19, 2020 • edited Loading

keljtanoski commented Nov 19, 2020

carbontwelve commented Dec 18, 2020

Youhan commented Dec 28, 2020

Rolando-Barbella commented Jan 5, 2021

liaoliaojun commented Jan 6, 2021

jlooper commented Jan 10, 2021

mittalvaibhav commented Jan 26, 2021

shuzootani commented Jan 29, 2021

rifandani commented Feb 1, 2021

cooskun commented Feb 2, 2021

Mancancode commented May 24, 2021

MiguelAngelParedesBustos commented May 24, 2021

darekkay commented May 31, 2021

patoncrispy commented Jun 19, 2021

mpakaris commented Jun 22, 2021

danielbachhuber commented Jun 23, 2021

lohnsonok commented Jul 10, 2021

88brmig commented Jul 30, 2021 • edited Loading

coolcorexix commented Aug 4, 2021 • edited Loading

emmaroland32 commented Aug 11, 2021

jakecausier commented Aug 25, 2021

alexcroox commented Nov 19, 2020 •

edited

Loading

SimonPrague commented Nov 19, 2020 •

edited

Loading

alexcroox commented Nov 19, 2020 •

edited

Loading

audn commented Nov 19, 2020 •

edited

Loading

seankndy commented Nov 19, 2020 •

edited

Loading

seankndy commented Nov 19, 2020 •

edited

Loading

88brmig commented Jul 30, 2021 •

edited

Loading

coolcorexix commented Aug 4, 2021 •

edited

Loading