Lines Matching +full:deploy +full:- +full:book

3 \fBdevelopers\fR \- Developer Guide
6 So, you've decided to use npm to develop (and maybe publish/deploy)
16 then do \fBman npm\-thing\fP to get the documentation on a particular
48 git://github\.com/user/project\.git#commit\-ish
49 git+ssh://user@hostname:project\.git#commit\-ish
50 git+http://user@hostname/project/blah\.git#commit\-ish
51 git+https://user@hostname/project/blah\.git#commit\-ish
55 The \fBcommit\-ish\fP can be any tag, sha, or branch which can be supplied as
73 So, \fBnode\-foo\fP and \fBbar\-js\fP are bad names\.  \fBfoo\fP or \fBbar\fP are better\.
76 A semver\-compatible version\.
89 least a basic smoke\-test command as the "scripts\.test" field\.
117 …same pattern rules \fIhttps://git\-scm\.com/book/en/v2/Git\-Basics\-Recording\-Changes\-to\-the\-R…
147 \fB\|\.lock\-wscript\fP
151 \fB\|\.wafpickle\-*\fP
157 \fBnpm\-debug\.log\fP
193 changes in real time without having to keep re\-installing it\.  (You do
194 need to either re\-link or \fBnpm rebuild \-g\fP to update compiled packages,
211 npm install \. \-g
224 Use \fBnpm ls \-g\fP to see if it's there\.
230 cd \.\./some\-other\-folder
231 npm install \.\./my\-package
237 Then go into the node\-repl, and try using require("my\-thing") to