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

thoughts about enabling warnings? #6

Closed
jokeyrhyme opened this issue May 29, 2017 · 1 comment
Closed

thoughts about enabling warnings? #6

jokeyrhyme opened this issue May 29, 2017 · 1 comment

Comments

@jokeyrhyme
Copy link

There are node options to enable stack traces for deprecations, warnings, and synchronous IO

node ---help

  --trace-deprecation        show stack traces on deprecations
  --trace-warnings           show stack traces on process warnings
  --trace-sync-io            show stack trace when use of sync IO

Do you think it's a good idea to enable these for development?

Do you think there's a problem with having these enabled in production builds?

@BretFisher
Copy link
Owner

Hey @jokeyrhyme so a few thoughts, but I'm no tracing expert.

  • This isn't docker related, whatever you'd do normally in Node, you'd do in a container when related to logging output and debugging/tracing.
  • I'd assume you'd run these on occasion in development or during CI testing.
  • I wouldn't recommend running them in production, to prevent unnecessary log entries.
  • I have no idea if they create "problems". I've never used them in prod.

Since this isn't a feature or bug request, I'm going to close the issue, but feel free to continue discussion.

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

No branches or pull requests

2 participants