-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(atomic): migrate to Tailwindcss v3 #1718
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,7 +6,7 @@ import html from 'rollup-plugin-html'; | |
import {inlineSvg} from 'stencil-inline-svg'; | ||
|
||
import tailwind from 'tailwindcss'; | ||
import postcssNesting from 'postcss-nested'; | ||
import tailwindNesting from 'tailwindcss/nesting'; | ||
import atImport from 'postcss-import'; | ||
import focusVisible from 'postcss-focus-visible'; | ||
import autoprefixer from 'autoprefixer'; | ||
|
@@ -113,9 +113,9 @@ export const config: Config = { | |
plugins: [ | ||
atImport(), | ||
mixins(), | ||
tailwindNesting(), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We have to use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. With this, we are getting an issue with mixins & nesting, the following doesn't work (same pattern as used in result templates): /* Mixin with nesting */
@define-mixin test-mixin {
input {
background-color: red;
}
}
div {
@mixin test-mixin;
} The fix is to reuse |
||
tailwind(), | ||
focusVisible(), | ||
postcssNesting(), | ||
autoprefixer(), | ||
], | ||
}), | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure why it was a dependency ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, hum, I think it can indeed be seen as a dev dependency, because it's not actually "shipped" to our clients, like they won't actually download and install tailwind when they
npm install @coveo/atomic