report: add new command #7611
report: add new command #7611
Conversation
Just post it to some kind of pastebin with 1 month expiration time imho. |
|
I like this! I do think it's going to take a little effort to land this, but now is probably as good a time as ever to get this moving along. This is an actual honest-to-gosh feature in npm, and as such needs a little extra effort to get right:
It would be fantastic to actually implement #5214, as we've been wanting this for nearly a year, so I'm willing to budget some of npm's time towards making sure this keeps moving forward. Thanks, @watilde! |
Add to give better unicode defaults by interrogating the locale
It can either effeciently fetch package metadata from the registry, or else it falls back to adding the package to the cache and then loading data from there. It also provides facilities for fetching shrinkwrap and bundled dependency data.
|
What happens on issues/new if the user is not logged in to github? |
|
Sorry for my late reply, @rlidwka Thanks for your information! I'll use it a little, but maybe I can't decide to include that to this patch in this time.. @othiym23 Sounds great! I'm going to added a document in @smikes Thanks for your comment, Redirect to this URL, after logged in report process will go well. |
|
1 down, 3 to go! Thanks for the docs! By the way, I think this will probably be something that lands after the release of |
|
@othiym23 I agreed to be something that lands after the release of npm@3. I'll git rebase |
|
This has been moved to the npm roadmap, which we're using instead of the confusing @watilde -san, once |
| body = "npm-debug.log:\n" | ||
| body += "```\n" | ||
| body += fs.readFileSync(npmDebugLog) | ||
| body += "```\n" |
There was a problem hiding this comment.
I think that it should ask user for input like:
What were you trying to do?
Any other comments?
Stuff like that. Also, maybe write to a file and then let the user edit it before sending it off?
Hi, I added report command for fixing #5214. That proposal might make support useful, people become needn't bring manually a npm-debug.log to the issue description in GitHub.
Well, I'd like to use
gistbut I think it might makes npm a little bit complex so I've built in this way.See also: #5214 (comment)
Thanks.