-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
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
Impossible to remove localhost
from ignoredHostnames
#30
Comments
Good catch! Thanks a lot. I have just released v1.0.1 to fix this issue. You can now provide an empty export default defineNuxtConfig({
modules: ['@nuxtjs/plausible'],
plausible: {
ignoredHostnames: [],
},
}) |
Thank you for the quick fix and release! |
This did not fix the problem. I tried updating the module to v1.0.1 and replacing After updating, the plugin types also broke: I had to manually add the types that were previously created by Nuxt automatically. This might be related to the "The inferred type of 'default' cannot be named without a reference to ..." warnings in the |
…host` (fixes #30)
@obulat Thanks a lot for the follow-up. Indeed, the plugin types where broken as of recent changes to the Nuxt module builder. This should be fixed with v1.0.2. Also, |
Thank you again for quick fix and release, @johannschopplich ! It's really fixed now, and we are about to migrate to the latest version :) |
Description
The
trackLocalhost
option is deprecated, but the new way of setting this asignoredHostnames: []
doesn't work."localhost" is always added to the
ignoredHostnames
array in the module setup.When I added a log at the top of the setup, I see that
options.ignoredHostnames
array always contains "localhost". If you set the value ofignoredHostnames
to something else, like["none"]
, then this value is added to the default["localhost"]
array instead of replacing it.The text was updated successfully, but these errors were encountered: