Also: if it's set up to report-npats, then report a package lacking a test script as well. I want to be able to highlight which packages are covered and which aren't.
[fyi: this is mostly me talking out the issue I've run into to see if you've seen something similar]
Started on this: https://github.com/DTrejo/node-report
My package runs fine all alone, and successfully saves results to the iriscouch.
However it does not work when my package is run via npm.
Relevant lines in lifecycle.js
I run this code to test whether my package integrates well with npm:
npm config set npat true
npm install gss
npm config set npat false
When I do this, my package prints that it is trying to make a request to my couchDB, but then the callback never fires.
If request is doing something weird, and the weirdness only manifests when run via npm, then I should probably run the node debugger on npm.
so don't worry much about looking deeply into this. I still have one avenue to pursue: running a debugger on npm and seeing why request acts weird. However if after a quick scan of this issue you can figure out what's going on, that would be much appreciated!
Isn't this a duplicate of #2504 ?
This issue is very old, is it still relevant?
Pour one out for unimplemented unworkable but still appealing ideas.
Readdressing a year and a half later, the Node and npm communities have gone one way, and this pointed the other. We're starting to look at the idea of global hooks to do things like this, and there are features under discussion for the npm web site and primary registry that also point at the same idea of tracking quality metrics over time. That said, the sense of the team right now is that npat is effectively deprecated, and should be actually deprecated at some point, because it's at least a little at odds with current packaging conventions (i.e. people using files to strip tests out of published packages). As such, this fine idea has finally met its end. 🍻 out for npat-report. It was a good idea.