npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

I kinda hate this 3 day close rule

I submitted a legit issue with NPM’s error messages. It got closed 3 days later. With holidays etc I feel this 3 day rule is too restrictive. It’s too restrictive the rest of the time and doubly so during any sort of holiday.

We can extend it to 7 days, but generally #support questions that don’t get answers right away are no longer worth responding to, because folks have usually moved on by then. Does extending to 7 sound good to you?

7 seems pretty fair. Where do I put stuff like “this error message is misleading” if #support doesn’t work?

It depends. Why not make a PR with what you think the error message should be?

I don’t understand what it’s doing well enough to make a PR suggesting a better version. The error message is saying “do this” but then I do that and I get the error again.

Should I just submit again and hope someone sees it before the holiday weekend?

sounds like a good one for #support or, if you have a reproducible bug, #bugs

Submitted and got " This topic will close 7 days after the last reply" – WOW I’m kinda amazed that happened and so quickly, thanks much