You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 26, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: