Tailwind CSS integration package #2745
Conversation
…feat/tailwind-integration
refactor: script reworked in purpose to be able to run via node
asvae
force-pushed
the
feat/tailwind-integration
branch
from
b5ea71c to
8d95a78
Compare
packages/docs/src/page-configs/styles/tailwind/code-examples/configuring.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
We're very close, but there are still some sharp edges.
I also updated docs a bit, hope you won't mind 😋.
I would suggest checking my comments, then asking @rustem-nasyrov or @LighthouseKeeperYN to try the flow on new project (one person tailwind -> vuestic, second - vuestic -> tailwind), then do final tweaks based on feedback.
There was a problem hiding this comment.
I don't like bin commands name. sync-tailwind what does it mean? Let's imagine I'm new developer on project, how should I know what this command does? I would rename it to sync-tailwind-with-vuestic. or "vuestic sync-with-tailwind" "vuestic sync-to-tailwind". No winner yet. You can keep it as is. I hope there will be a plugin later.
Open docs? :) But i see your point, will rename them. |
Related: #2184
Closes: #1287
Closes: #731
Description
@vuestic/tailwindpackage for syncing Tailwind CSS -> Vuestic UI colors and breakpoint configs.reset.cssfrom docs.griddocs page was totally rewritten .While testing i've found out, that our color config does't understand colors with separators (red-500 is broken, but red500 is ok for example). Will investigate and fix it within another issue.
Types of changes