-
Notifications
You must be signed in to change notification settings - Fork 3
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
Trimming the trailing newline (and more tips on migrating from execa
/other packages)
#36
Comments
I think we just need to document it, as it isn't the best thing to do by default (want to avoid implementing the same magic execa and others did, keeping things straight forward) We probably just need a section explaining how to migrate |
execa
/other packages)
I'm happy to contribute to such a section once we settle on what structure it should follow! |
Sure, I think we should probably add a top level section for migration with a subsection for execa Things in particular we should note:
Let's try avoid listing every possible difference though and stick to the main few that might trip people up |
that'd be great, I maybe want to migrate from I recently migrated |
When migrating
execa
totinyexec
in some projects, I've ran into a difference in the default behavior whereexeca
would trim the trailing newline by default (https://github.com/sindresorhus/execa/blob/3fc804916d60b0b2e774a3642bd9815388caf7af/docs/lines.md?plain=1#L56-L63), whereastinyexec
wouldn't. I see two possible solutions for this issue:tinyexec
. This could potentially introduce some unwanted complexity as disabling the behavior (stripFinalNewline
option inexeca
) should also be supported then..trim()
on the returned output.The text was updated successfully, but these errors were encountered: