N-API PR lands

I've mentioned a few times that we have been working with the community on an ABI stable module API for Node.js native modules (N-API).  Based on earlier discussion at the latest vm summit (see https://developer.ibm.com/node/2017/03/07/node-js-vm-summit-moving-forward-with-n-api/ for details) the goal was to get it into master as an experimental feature so that it can be included...  Continue reading N-API PR lands

Easier Node.js code coverage generation

Last month I mentioned that the nightly code coverage runs were already paying dividends. We'd seen that coverage for the core Node.js project had increased by ~1% for each of javascript and C++:  node-js-code-coverage-data-paying-dividends.  This trend continues with coverage continuing to rise.  A big thank you and high five for all the members of...  Continue reading Easier Node.js code coverage generation

Announcing node-report version 2.1.0 – the essential diagnostic for Node.js applications

A summary diagnostic report for Node.js was introduced in NodeReport – first failure data capture for Node.js. The report can be triggered on unhandled exceptions, fatal errors, signals and by calling JavaScript APIs. It contains key information about the JavaScript application and the Node.js run-time, including JavaScript and C++ stacks, V8 heap statistics, per-process...  Continue reading Announcing node-report version 2.1.0 – the essential diagnostic for Node.js applications

Node.js Code Coverage Data – Paying Dividends

If you want to improve, having the right data is often critical.  It has been 3 months  since nightly code coverage runs were added to the Node.js project (12 October 2016).  You can see the nightly runs here: https://coverage.nodejs.org/. Looking at the results we can see that we've made progress since that time:   JavaScript...  Continue reading Node.js Code Coverage Data – Paying Dividends

Code coverage for Node.js drives improvements

As announced in a recent weekly update on nodejs.org: https://nodejs.org/en/blog/weekly-updates/weekly-update.2016-11-11/ nightly code coverage data is now available at coverage.nodejs.org. It's great to see this data being available and also that there have already been PRs which have used the data in order to improve coverage: test: increase coverage of process.emitWarning #9556 test:ensure nextTick is not scheduled...  Continue reading Code coverage for Node.js drives improvements