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
Prior to v10.5.0 there was possibility to directly redirect npm pack output to file and retrieve tarball file name for given package. Starting from 10.5.0 and above stdout is being polluted by prepare scripts output and command itself.
@falsyvalues This change was introduced as a fix to correct the regression. Follow discussion on this PR #7158 to get more background on this change. You can use this flag foreground-scripts or --silent to get expected output result.
@milaninfy Will I get the reasoning, result remains the same - breaking for end user. Also --silent won't help because it mutes only script call not the result.
@falsyvalues Apologies I must have thought something else when I suggested --silent flag
but here is the output with npm pack --foreground-scripts=false > test2.txt.
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Prior to v10.5.0 there was possibility to directly redirect
npm pack
output to file and retrieve tarball file name for given package. Starting from 10.5.0 and above stdout is being polluted by prepare scripts output and command itself.Expected Behavior
npm pack
should output to std only tarball file name as it was before otherwise its a breaking change.Steps To Reproduce
npm pack
and redirect stdout to file e.g.npm package > package-name
package-name
file contentEnvironment
The text was updated successfully, but these errors were encountered: