Skip to content
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

Add forwardLog option to NuxtConfiguration #5728

Closed
potato4d opened this issue May 14, 2019 · 5 comments · Fixed by #5784
Closed

Add forwardLog option to NuxtConfiguration #5728

potato4d opened this issue May 14, 2019 · 5 comments · Fixed by #5784

Comments

@potato4d
Copy link

What problem does this feature solve?

in Nuxt v2.7.0 or later, nuxt dev forwards SSR's console.log to the front end.
However, if you have a large number of logs, you do not necessarily want to forward them to the front end.

To that end, it would be nice to be able to turn it off from nuxt.config.js.

What does the proposed changes look like?

  1. Add a flag (Boolan) whether to transfer to NuxtConfiguration
  2. Make a change to make it work properly (I would like to send a Pull Request for it)

thanks.

This feature request is available on Nuxt community (#c9214)
@ghost ghost added the cmty:feature-request label May 14, 2019
@potato4d
Copy link
Author

The key name may be better, such as ignoreDevLogs.ssr.

@potato4d
Copy link
Author

I think that there is something like this.
magitek-telescope@6ea3080

Also, is it better to be able to change other logs? (I think that another discussion is necessary)

@clarkdo
Copy link
Member

clarkdo commented May 22, 2019

@potato4d The SSR log has been put into a group by #5770 , so it can be collapsed now, does it meet your requirement ?

@potato4d
Copy link
Author

@clarkdo
I will check it within a few days!
thanks

@clarkdo
Copy link
Member

clarkdo commented May 22, 2019

@potato4d I proposed a pr for more fine-grained configuration for SSR log

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

Successfully merging a pull request may close this issue.

4 participants