Closed kakinouchi closed 3 years ago
I think the best way to do this will be to support using a tailwind.config.js
for more advanced setups. Ultimately it may be worth adding support for custom syntax, but I think we're better off keeping it simple in the :tailwind/config
and then leaving advanced usage to a true tailwind.config.js
as suggested in #3
That's true, I agree with you. You can close this(#2) issue, thank you.
I'm sorry if I'm wrong to ask questions here.
I have two questions about setting
:tailwind/config
require
notation? (e.g. to setplugins: [require('@tailwindcss/ui')]
Thank you.