npm 'No repository field' warning


Let's look at a few options for the "No repository field".

Experimenting
If experimenting / playing around (will not be publishing the project and/or do not need version control) then ignore the warning (see alternative to supress below)
npm WARN play@1.0.0 No repository field.
Supress Warning
We may supress the "No repository field" by adding the "private" flag as shown here to our "package.json".
"private": true
Add Version Control
We add version control by adding a "repository" section to our "package.json" file as shown.

(using actual url)
"repository": {
  "type": "git",
  "url": "git://github.com/username/repository.git"
}
Fussy File Path (Missing Dot)
Assure you have the first form shown
Works
{TestLab} = require('./test-lab');

Does Not Work
{TestLab} = require('/test-lab');

Does Not Work
{TestLab} = require('test-lab');
}
Debugging Locally External File
Assure you have the first form shown
Say you have separate projects module S (source) and module C (client). A and C live in different project directories.

If debugging mehod S.foo.go() from module C, then we need to open S.foo and set a breakpoint in method go().
}