Skip to content

fix: skip creation of log directory if logs-max is set to 0 - #7033

Merged
wraithgar merged 7 commits into
npm:latestfrom
JJ:patch-2
Nov 29, 2023
Merged

fix: skip creation of log directory if logs-max is set to 0#7033
wraithgar merged 7 commits into
npm:latestfrom
JJ:patch-2

Conversation

@JJ

@JJJJ commented Nov 28, 2023

Copy link
Copy Markdown
Contributor

If no logs are needed, don't call the task that creates the directory anyway. This goes mainly to fix#7032. Also, typo.

After all, it can fail.
This goes mainly to fixnpm#7032
@JJ
JJ requested a review from a team as a code ownerNovember 28, 2023 14:08
Comment threadlib/npm.js Outdated
@JJJJ changed the title Skip creation of log directory if it's set to an empty stringSkip creation of log directory if logs-max is set to 0Nov 29, 2023
@JJ
JJ requested a review from wraithgarNovember 29, 2023 11:47
@wraithgarwraithgar changed the title Skip creation of log directory if logs-max is set to 0fix: skip creation of log directory if logs-max is set to 0Nov 29, 2023
@wraithgar

Copy link
Copy Markdown
Contributor

npm run lintfix should get you all green now.

Comment threadtest/lib/utils/exit-handler.js Outdated
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Why is npm run writing into the .npm/_logs directory or creating it?

2 participants

@JJ@wraithgar