paulmillr / console-polyfill Goto Github PK

This is a small issue, but it's easily fixed.
My automated build script does a bower install which gives the following error:

##[error]bower console-polyfill#~0.2.1     invalid-meta console-polyfill is missing "ignore" entry in bower.json

I've set the build to continue on this error, and it works, however it now shows all my builds as "Partially succeeded".

By adding the line

"ignore": [],

in bower.json, the warning should go away.

Any chance you could push a dot release to npm to pick up the most recent changes in master?

"Setting a property that has only a getter."

Uncaught TypeError: Cannot set property memory of #<Console> which has only a getter
    at window.console (<anonymous>:14:45)
    at <anonymous>:16:3
    at Object.InjectedScript._evaluateOn (<anonymous>:895:140)
    at Object.InjectedScript._evaluateAndWrap (<anonymous>:828:34)
    at Object.InjectedScript.evaluate (<anonymous>:694:21)

I don't know if this will make it in to a release, but it might be a good idea to wrap these assignments in a try/catch.

This polyfill is missing some methods from the console API, like console.table.

If that's relevant, I can send a PR for it. I'm not sure if they've been left out intentionally.

It would be awesome to get this on NPM.

Hi. Thank you for good script.

I want use on CDN, and try create register patch like this

If no problem, I try send pull request.

Interested in this polyfill, but I am curious about the choice of string.split versus declaring arrays from the start. Ran a test and the results seem to favor moving away from string split. Please check out the jsperf test As a trivial downside, the change adds a few more characters to the declaration of methods in the form of single quotes.

In IE8 (and possibly newer versions as well), typeof console.log is object instead of function. I know there are other solutions that account for this and perhaps this one is not intended to do that, but it would be nice if it did so that it is safe to call a wrapper function like

function() {
    console.log.apply(console, arguments);
    /* (do something else here -- perhaps call cloud log aggregation API) */
}

Getting this error in Chrome Canary:

Uncaught TypeError: Cannot set property memory of #<Console> which has only a getter

It is happening on line 18, which is setting console.memory, but it's not allowed anymore I guess. This will probably make it into Chrome eventually, so good to fix now. I'll look into a quick fix.