node package manager
Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »



Quickly loads a remote page using phantomjs to check if there are any JavaScript console errors.


Build status dependencies devdependencies semantic-release

Install and use

npm install -g clean-console
// assumes phantomjs is installed
clean-console -i <url>

Note: only actual exceptions will be logged, failed console.assert statements DO NOT cause a true browser error (unlike nodejs).

A good pattern to unify nodejs/browser assertion handling is to wrap assertions into helper method:

function really(condition, message) {
    console.assert(condition, message); // stops nodejs execution
    if (!condition) {
        // stop execution in a browser
        throw new Error(condition.toString() + ' failed, ' + message);


Seems the latest PhantomJs 2 generates errors when using console.error and console.assert by default.

Small print

Author: Gleb Bahmutov © 2013

License: MIT - do anything with the code, but don't blame me if it does not work.

Support: if you find any problems with this module, email / tweet / open issue on Github