--- /dev/null
+.TH "NPM\-CONFIG" "3" "October 2016" "" ""
+.SH "NAME"
+\fBnpm-config\fR \- Manage the npm configuration files
+.SH SYNOPSIS
+.P
+.RS 2
+.nf
+npm\.commands\.config(args, callback)
+var val = npm\.config\.get(key)
+npm\.config\.set(key, val)
+.fi
+.RE
+.SH DESCRIPTION
+.P
+This function acts much the same way as the command\-line version\. The first
+element in the array tells config what to do\. Possible values are:
+.RS 0
+.IP \(bu 2
+\fBset\fP
+ Sets a config parameter\. The second element in \fBargs\fP is interpreted as the
+ key, and the third element is interpreted as the value\.
+.IP \(bu 2
+\fBget\fP
+ Gets the value of a config parameter\. The second element in \fBargs\fP is the
+ key to get the value of\.
+.IP \(bu 2
+\fBdelete\fP (\fBrm\fP or \fBdel\fP)
+ Deletes a parameter from the config\. The second element in \fBargs\fP is the
+ key to delete\.
+.IP \(bu 2
+\fBlist\fP (\fBls\fP)
+ Show all configs that aren't secret\. No parameters necessary\.
+.IP \(bu 2
+\fBedit\fP:
+ Opens the config file in the default editor\. This command isn't very useful
+ programmatically, but it is made available\.
+
+.RE
+.P
+To programmatically access npm configuration settings, or set them for
+the duration of a program, use the \fBnpm\.config\.set\fP and \fBnpm\.config\.get\fP
+functions instead\.
+.SH SEE ALSO
+.RS 0
+.IP \(bu 2
+npm apihelp npm
+
+.RE
+