Provide getReport API to return the contents of node-report.

Merge in the changes from node-report 2.0

Author: hhellyer

.gitignore

@@ -39,6 +39,7 @@
 
 # Package files
 NodeReport*.txt
+node-report*.txt
 npm-debug.log
 nodereport-*.tgz
 nodereport_test.log

CHANGES.md

@@ -1,3 +1,27 @@
+2017-02-09, Version 2.0.0
+=========================
+
+ * mac: Fix compilation errors (Howard Hellyer)
+
+ * Rename nodereport module to node-report (Richard Chamberlain)
+
+ * Fix source directory for install target (Richard Lau)
+
+ * aix: skip command line check for test-fatal-error (Richard Lau)
+
+ * Add the list of library files loaded by the process to nodereport. (Howard Hellyer)
+
+ * docs: AIX supports triggering on USR2 signal (Richard Lau)
+
+ * Fix behaviour on exception to match node default (Richard Chamberlain)
+
+ * Adds the command line used to start the node process to nodereport. (Howard Hellyer)
+
+ * Opt-in hooks and signal by default (Richard Chamberlain)
+
+ * Fix for clang warning: libstdc++ is deprecated (Richard Chamberlain)
+
+
 2016-12-12, Version 1.0.7
 =========================
 

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to nodereport
+# Contributing to node-report
 
 ## Code of Conduct
 
@@ -8,7 +8,7 @@ The [Node.js Code of Conduct][] applies to this repo.
 
 ## Code Contributions
 
-The nodereport project falls under the governance of the post-mortem
+The node-report project falls under the governance of the post-mortem
 working group which is documented in:
 https://github.com/nodejs/post-mortem/blob/master/GOVERNANCE.md
 

GOVERNANCE.md

@@ -1,5 +1,5 @@
-# nodereport Project Governance
+# node-report Project Governance
 
-The nodereport project falls under the governance of the post-mortem
+The node-report project falls under the governance of the post-mortem
 working group which is documented in:
 https://github.com/nodejs/post-mortem/blob/master/GOVERNANCE.md.

LICENCE.md

@@ -1,10 +1,10 @@
 The MIT License (MIT)
 =====================
 
-Copyright (c) 2016 nodereport contributors
+Copyright (c) 2016 node-report contributors
 --------------------------------------------------
 
-*nodereport contributors listed at <https://github.com/nodejs/nodereport/blob/master/AUTHORS>*
+*nodereport contributors listed in <https://github.com/nodejs/nodereport/blob/master/package.json>*
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 

MAINTAINER.md

@@ -1,15 +1,15 @@
-# Instructions for maintainers of the nodereport project
-
-## Publishing to the npm registry
-
-The nodereport project is published as an npm native module
-
-For each publish to npm:
-
- - update the version property in the package.json file, incrementing the major, minor and patch level as appropriate 
- - update the CHANGES.md file with a list of commits since last release
- - commit CHANGES.md and package.json to nodereport master branch
- - tag commit with an annotated tag
- - git checkout and npm publish the nodereport package
-
-Suggested tooling is the slt-release script documented here: https://github.com/strongloop/strong-tools
+# Instructions for maintainers of the node-report project
+
+## Publishing to the npm registry
+
+The node-report project is published as an npm native module
+
+For each publish to npm:
+
+ - update the version property in the package.json file, incrementing the major, minor and patch level as appropriate
+ - update the CHANGES.md file with a list of commits since last release
+ - commit CHANGES.md and package.json to node-report master branch
+ - tag commit with an annotated tag
+ - git checkout and npm publish the node-report package
+
+Suggested tooling is the slt-release script documented here: https://github.com/strongloop/strong-tools

README.md

@@ -1,4 +1,4 @@
-# nodereport
+# node-report
 
 Delivers a human-readable diagnostic summary, written to file.
 
@@ -14,18 +14,18 @@ Supports Node.js v4, v6 and v7 on Linux, MacOS, Windows and AIX.
 ## Usage
 
 ```bash
-npm install nodereport
-node -r nodereport app.js
+npm install node-report
+node -r node-report app.js
 ```
-A NodeReport will be triggered automatically on unhandled exceptions and fatal
+A report will be triggered automatically on unhandled exceptions and fatal
 error events (for example out of memory errors), and can also be triggered
 by sending a USR2 signal to a Node.js process (AIX/Linux/MacOS only).
 
-A NodeReport can also be triggered via an API call from a JavaScript
+A report can also be triggered via an API call from a JavaScript
 application.
 
 ```js
-var nodereport = require('nodereport');
+var nodereport = require('node-report');
 nodereport.triggerReport();
 ```
 The content of a NodeReport can also be returned as a JavaScript string via an
@@ -40,27 +40,27 @@ The API can be used without adding the automatic exception and fatal error
 hooks and the signal handler, as follows:
 
 ```js
-var nodereport = require('nodereport/api');
+var nodereport = require('node-report/api');
 nodereport.triggerReport();
 ```
 
-Content of the NodeReport consists of a header section containing the event
+Content of the report consists of a header section containing the event
 type, date, time, PID and Node version, sections containing JavaScript and
 native stack traces, a section containing V8 heap information, a section
 containing libuv handle information and an OS platform information section
-showing CPU and memory usage and system limits. An example NodeReport can be
+showing CPU and memory usage and system limits. An example report can be
 triggered using the Node.js REPL:
 
 ```
 $ node
-> nodereport = require('nodereport')
+> nodereport = require('node-report')
 > nodereport.triggerReport()
-Writing Node.js report to file: NodeReport.20161020.091102.8480.001.txt
+Writing Node.js report to file: node-report.20161020.091102.8480.001.txt
 Node.js report completed
 >
 ```
 
-When a NodeReport is triggered, start and end messages are issued to stderr
+When a report is triggered, start and end messages are issued to stderr
 and the filename of the report is returned to the caller. The default filename
 includes the date, time, PID and a sequence number. Alternatively, a filename
 can be specified as a parameter on the `triggerReport()` call.
@@ -74,14 +74,15 @@ nodereport.triggerReport("myReportName");
 Additional configuration is available using the following APIs:
 
 ```js
+var nodereport = require('node-report/api');
 nodereport.setEvents("exception+fatalerror+signal+apicall");
 nodereport.setSignal("SIGUSR2|SIGQUIT");
 nodereport.setFileName("stdout|stderr|<filename>");
 nodereport.setDirectory("<full path>");
 nodereport.setVerbose("yes|no");
 ```
 
-Configuration on module Initialization is also available via environment variables:
+Configuration on module initialization is also available via environment variables:
 
 ```bash
 export NODEREPORT_EVENTS=exception+fatalerror+signal+apicall
@@ -93,14 +94,14 @@ export NODEREPORT_VERBOSE=yes|no
 
 ## Examples
 
-To see examples of NodeReports generated from these events you can run the
-demonstration applications provided in the nodereport github repository. These are
+To see examples of reports generated from these events you can run the
+demonstration applications provided in the node-report github repository. These are
 Node.js applications which will prompt you to trigger the required event.
 
-1. `api.js` - NodeReport triggered by JavaScript API call.
-2. `exception.js` - NodeReport triggered by unhandled exception.
-3. `fatalerror.js` - NodeReport triggered by fatal error on JavaScript heap out of memory.
-4. `loop.js` - looping application, NodeReport triggered using kill `-USR2 <pid>`.
+1. `api.js` - report triggered by JavaScript API call.
+2. `exception.js` - report triggered by unhandled exception.
+3. `fatalerror.js` - report triggered by fatal error on JavaScript heap out of memory.
+4. `loop.js` - looping application, report triggered using kill `-USR2 <pid>`.
 
 ## License
 

binding.gyp

@@ -13,12 +13,6 @@
           "libraries": [ "dbghelp.lib", "Netapi32.lib", "PsApi.lib" ],
           "dll_files": [ "dbghelp.dll", "Netapi32.dll", "PsApi.dll" ],
         }],
-        ["OS=='mac'", {
-          "xcode_settings": {
-            'CLANG_CXX_LIBRARY': 'libc++',
-            'CLANG_CXX_LANGUAGE_STANDARD':'c++11',
-          }
-        }],
       ],
       "defines": [
         'NODEREPORT_VERSION="<!(node -p \"require(\'./package.json\').version\")"'

demo/api_call.js

@@ -1,5 +1,5 @@
-// Example - generation of NodeReport via API call
-var nodereport = require('nodereport');
+// Example - generation of report via API call
+var nodereport = require('node-report');
 var http = require("http");
 
 var count = 0;
@@ -8,12 +8,12 @@ function my_listener(request, response) {
   switch(count++) {
   case 0:
     response.writeHead(200,{"Content-Type": "text/plain"});
-    response.write("\nRunning NodeReport API demo... refresh page to trigger NodeReport");
+    response.write("\nRunning node-report API demo... refresh page to trigger report");
     response.end();
     break;
   case 1:
     response.writeHead(200,{"Content-Type": "text/plain"});
-    // Call the nodereport module to trigger a NodeReport
+    // Call the node-report module to trigger a report
     var filename = nodereport.triggerReport();
     response.write("\n" + filename + " written - refresh page to close");
     response.end();

demo/exception.js

@@ -1,5 +1,5 @@
-// Example - generation of NodeReport on uncaught exception
-require('nodereport').setEvents("exception");
+// Example - generation of report on uncaught exception
+require('node-report').setEvents("exception");
 var http = require("http");
 
 var count = 0;
@@ -8,7 +8,7 @@ function my_listener(request, response) {
   switch(count++) {
   case 0:
     response.writeHead(200,{"Content-Type": "text/plain"});
-    response.write("\nRunning NodeReport exception demo... refresh page to cause exception (application will terminate)");
+    response.write("\nRunning node-report exception demo... refresh page to cause exception (application will terminate)");
     response.end();
     break;
   default: