Don't output `console.log`s in production (don't use console.log directly)

[coopy]

Plotly.js uses raw console.log statements to print info, warning, and error messages. Instead, it should use an abstract logger so we can silence warnings in production. Something like https://github.com/FormidableLabs/abstract-log that lets us configure a null transport in production for anything but errors.

As an example of this happening, try typing some HTML into the rich annotations editor. Before you've closed the opening tag, svg_text_utils.js spews errors for every update.

[etpinard]

And we should probably add the no-console eslint rule to the src .eslintrc.

[n-riesco]

I was thinking of submitting a PR to replace all the occurrences of console.log under src/ with lib.log. Would that be OK?

[etpinard]

@n-riesco I think we should at least expose a config argument so that users that want to see the logs can see them, using:

Plotly.plot('graph', data, layout, { verbose: true });

[mdtusz]

Agreed on this - probably would be good to swap most console.log statements to Lib.log, but I still think there are some true errors/warnings that should remain (e.g. things like calling Plotly.plot with invalid arguments).

[etpinard]

but I still think there are some true errors/warnings that should remain

maybe throwing errors would be better.

[mdtusz]

😑 ...

Yep.