Skip to content
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.

Using Tailwind's exposeConfig #14

Open
gekkedev opened this issue Feb 19, 2021 · 0 comments
Open

Using Tailwind's exposeConfig #14

gekkedev opened this issue Feb 19, 2021 · 0 comments

Comments

@gekkedev
Copy link
Contributor

Recommending to enable exposeConfig seems acceptable for dev environments, but that would accidentally be applied to production by many. Even if nuxt-breaky itself does not get copied in a prod build, this setting still applies and does no good. Recommening a responsible setting would be the easy way, but from a different angle:
Maybe there is a better hook that can be used to determine a project's responsiveness data? For example, the Tailwind config viewer (no included in the Nuxt-Tailwind-module doesn't seem to require that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant