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
currently vivliostyle-cli logs to stderr, even if the built was successfully:
stdout: "\ndata/main.pdf has been created.\n"
stderr: "- Collecting build config\nℹ Launching build environment\n(node:13) [DEP0040] DeprecationWarning: The punycodemodule is deprecated. Please use a userland alternative instead.\n(Usenode --trace-deprecation ... to show where the warning was created)\nℹ Building pages\nℹ Building PDF\nℹ Processing PDF\n🎉 Built successfully.\n"
It would be nice to only use stderr on failed builts, so that the vivliostyle-cli output can be parsed more easily.
Thanks!
anghenfil
The text was updated successfully, but these errors were encountered:
However, it is doubtful whether this setting should be used. The author of this library intentionally chose stderr as the default setting.
sindresorhus/ora#85
The reason it's stderr is so that it will not interfere with normal output. Most other spinners use stderr too.
Despite its name, stderr is sometimes used for diagnostic messages like build progress, not just error messages. In my personal opinion, it is preferable to follow convention and use stderr. If you find the output annoying, please consider using the --log-level silent option.
Hey,
currently vivliostyle-cli logs to stderr, even if the built was successfully:
stdout:
"\ndata/main.pdf has been created.\n"
stderr:
"- Collecting build config\nℹ Launching build environment\n(node:13) [DEP0040] DeprecationWarning: The
punycodemodule is deprecated. Please use a userland alternative instead.\n(Use
node --trace-deprecation ...to show where the warning was created)\nℹ Building pages\nℹ Building PDF\nℹ Processing PDF\n🎉 Built successfully.\n"
It would be nice to only use stderr on failed builts, so that the vivliostyle-cli output can be parsed more easily.
Thanks!
anghenfil
The text was updated successfully, but these errors were encountered: