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
The npm published versions of vuenut should not print their own debug info into console.log as it adds noise and obstructs the user's debugging (and it's commonly in debugging that I use Vuenut anyway). At least hide the console output behind a runtime flag that can be given to vuenut when instantiating it e.g. Vue.use(vuenut, { debug: true }).
The text was updated successfully, but these errors were encountered:
Hello,
The npm published versions of vuenut should not print their own debug info into console.log as it adds noise and obstructs the user's debugging (and it's commonly in debugging that I use Vuenut anyway). At least hide the console output behind a runtime flag that can be given to vuenut when instantiating it e.g.
Vue.use(vuenut, { debug: true })
.The text was updated successfully, but these errors were encountered: