Support
Quality
Security
License
Reuse
Coming Soon for all Libraries!
Currently covering the most popular Java, JavaScript and Python libraries. See a SAMPLE HERE.
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
What exactly are the rules for configuring postcss.config.js (mainly with tailwndcss)?
npm install tailwindcss postcss autoprefixer
Error: PostCSS plugin tailwindcss requires PostCSS 8.
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
npx tailwindcss init -p
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
import './css/tailwind.css'
-----------------------
npm install tailwindcss postcss autoprefixer
Error: PostCSS plugin tailwindcss requires PostCSS 8.
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
npx tailwindcss init -p
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
import './css/tailwind.css'
-----------------------
npm install tailwindcss postcss autoprefixer
Error: PostCSS plugin tailwindcss requires PostCSS 8.
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
npx tailwindcss init -p
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
import './css/tailwind.css'
-----------------------
npm install tailwindcss postcss autoprefixer
Error: PostCSS plugin tailwindcss requires PostCSS 8.
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
npx tailwindcss init -p
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
import './css/tailwind.css'
-----------------------
npm install tailwindcss postcss autoprefixer
Error: PostCSS plugin tailwindcss requires PostCSS 8.
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
npx tailwindcss init -p
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
import './css/tailwind.css'
-----------------------
npm install tailwindcss postcss autoprefixer
Error: PostCSS plugin tailwindcss requires PostCSS 8.
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
npx tailwindcss init -p
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
import './css/tailwind.css'
-----------------------
npm install tailwindcss postcss autoprefixer
Error: PostCSS plugin tailwindcss requires PostCSS 8.
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
npx tailwindcss init -p
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
import './css/tailwind.css'
-----------------------
// Example 2 fixed:
module.exports = {
plugins: [ // <= here we MUST use brackets!
... [function calls] ...
],
}
-----------------------
// Example 3:
const tailwindcss = require('tailwindcss');
const postcssPresetEnv = require('postcss-preset-env');
module.exports = {
plugins: {
tailwindcss,
postcssPresetEnv
},
}
"postcss": "^8.4.6",
"postcss-cli": "^9.1.0",
"tailwindcss": "^3.0.18",
-----------------------
// Example 3:
const tailwindcss = require('tailwindcss');
const postcssPresetEnv = require('postcss-preset-env');
module.exports = {
plugins: {
tailwindcss,
postcssPresetEnv
},
}
"postcss": "^8.4.6",
"postcss-cli": "^9.1.0",
"tailwindcss": "^3.0.18",
-----------------------
"postcss": {
"plugins": [
"postcss-import",
"tailwindcss",
"postcss-preset-env",
"autoprefixer",
"cssnano"
]
}
QUESTION
What exactly are the rules for configuring postcss.config.js (mainly with tailwndcss)?
Asked 2022-Mar-29 at 11:40The number of variants that exist to showcase how postcss.config.js
has to be configured is extremely confusing. There are examples (like the one at the tailwindcss
documentation) that use this:
// Example 1:
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
}
then there are those which require the libraries:
// Example 2:
module.exports = {
plugins: {
require('tailwindcss'),
require('postcss-preset-env')({
stage: 0,
'nesting-rules': true
})
},
}
Others require external libs before they configure module.exports
:
// Example 3:
const tailwindcss = require('tailwindcss');
const postcssPresetEnv = require('postcss-preset-env');
module.exports = {
plugins: {
tailwindcss,
postcssPresetEnv
},
}
and again some more that are necessary, when a configuration file that is not named according to the defaults has to be incorporated.
Today I get this error, when running yarn dev
with a postcss.config.js as show in Example 2:
Syntax Error: /[path]/_pod-test/postcss.config.js:3
require('tailwindcss'),
^^^^^^^^^^^
SyntaxError: Unexpected string
When I remove the line with "tailwindcss", the same thing happens for "postcss-preset-env":
Syntax Error: /Volumes/_III_/Z_WWW/_ZZZ PoD/_pod-test/postcss.config.js:3
require('postcss-preset-env')({
^^^^^^^^^^^^^^^^^^^^
SyntaxError: Unexpected string
When I then switch to a setup as shown in example 1, I get this error:
Syntax Error: Error: PostCSS plugin tailwindcss requires PostCSS 8.
Migration guide for end-users:
https://github.com/postcss/postcss/wiki/PostCSS-8-for-end-users
I do use postcss 8.3.9!
This all happens in a project that was setup with vue-cli
as a Vue2 project.
Which witch craft do I have to apply to make this setup work?
ANSWER
Answered 2021-Oct-26 at 14:58In your terminal run the below command to install tailwind css and its dependencies via npm.
npm install tailwindcss postcss autoprefixer
It is possible to get the error message that you mentioned when you try to run the project
Error: PostCSS plugin tailwindcss requires PostCSS 8.
Run the following code to uninstall previous installation and fix the error
npm uninstall tailwindcss postcss autoprefixer
npm install tailwindcss@npm:@tailwindcss/postcss7-compat@tailwindcss/postcss7-compat postcss@^7 autoprefixer@^9
Next, you need to generate both Tailwind and PostCSS config files
npx tailwindcss init -p
Your config files should look like this
postcss.config file
module.exports = {
plugins: {
tailwindcss: {},
autoprefixer: {},
},
};
tailwindcss.config file
module.exports = {
future: {
// removeDeprecatedGapUtilities: true,
// purgeLayersByDefault: true,
},
purge: [],
theme: {
extend: {},
},
variants: {},
plugins: [],
};
Finally, open up your main.js file and import the tailwind.css file containing the tailwind directives i.e
import './css/tailwind.css'
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
No vulnerabilities reported
Explore Related Topics