Feature Request: expose resolved Tailwind config within app

[homerjam]

I'm having a hard tie trying to access my Tailwind config in Nuxt in order to reference the breakpoints (screens) config (related issue).

It would be great if this module was able to provide the resolved config to avoid this issue.

[atinux]

Actually it creates tailwind.config.js at the root of your directory ;)

[homerjam]

Indeed! But it seems it can't be imported because of the import / module.exports incompatibility. I've worked around it by importing in nuxt.config.js and storing as an env vars. However it'd be great to be avoid this boilerplate code and to have the resolved (full) config available.

[atinux]

@homerjam could you make a reproduction by forking https://codesandbox.io/s/o4vn5pvp7q so I can better see what you are trying to achieve?

Please mention me so I can receive a notification

[homerjam]

Hi @atinux

https://codesandbox.io/s/nuxt-tailwindcss-import-config-example-ksgyc

[atinux]

Hi @homerjam

Could you try this?
https://tailwindcss.com/docs/configuration/#referencing-in-javascript

[homerjam]

@atinux I've updated the sandbox. I did try that before but it seems like a problem with importing the config to begin with - the resolveConfig function combines the defaults with your own AFAIK.

[homerjam]

I also tried specifying tailwind.config.js in the build.transpile section of nuxt.config, but this didn't have any effect...

[atinux]

Just found out this tweet: https://twitter.com/ClarkDu_/status/968885321017389056

We are investigating to find a workaround, also @pi0 told me that importing tailwind config resolver adds a lot of vendors:

So it may not be that good to actually import it in your Vue app 😬

[homerjam]

Ah ha! Although that tweet is quite an old one!

So it may not be that good to actually import it in your Vue app 😬

Noted - yes probably not worth importing the resolved config for my uses. Perhaps a better solution is to create a tailwind.json file with the resolved config beside the tailwind.css file...?

[clarkdo]

Hi @homerjam , the TypeError you mentioned above will be fixed in nuxt/nuxt#7070 .

After it's get merged, you can verify it by replacing nuxt with nuxt-edge and clearing node_modules/.cache