Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuxt global is leaking in the final build of application. However many modules reference this directly instead of refering to global name from configuration.
Can we use the globalName option in the nuxt config instead of $nuxt directly ? https://github.com/nuxt-community/axios-module/blob/dev/lib/plugin.js#L129
const $loading = () => (window.$nuxt && window.$nuxt.$loading && window.$nuxt.$loading.set) ? window.$nuxt.$loading : noopLoading
const $loading = () => (window.<%= options.globalName %> && window.<%= options.globalName %>.$loading && window.<%= options.globalName %>.$loading.set) ? window.<%= options.globalName %>$loading : noopLoading
The text was updated successfully, but these errors were encountered:
fd1f8ec
Thanks for report @jjelev
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
What problem does this feature solve?
Nuxt global is leaking in the final build of application. However many modules reference this directly instead of refering to global name from configuration.
Can we use the globalName option in the nuxt config instead of $nuxt directly ?
https://github.com/nuxt-community/axios-module/blob/dev/lib/plugin.js#L129
What does the proposed changes look like?
The text was updated successfully, but these errors were encountered: