How does console.log-wrapper compare to console-polyfill?

Console.log-wrapper goes beyond basic polyfilling by enhancing output readability and automatically loading Firebug Lite for full support in legacy browsers, whereas console-polyfill typically only adds missing console functions without extra features.

Can I use console.log-wrapper in Node.js?

No, it's designed for client-side browsers to handle cross-browser inconsistencies; Node.js has a consistent console, so using it there would be redundant and unsupported.

How to prevent Firebug Lite from loading with console.log-wrapper?

The README doesn't provide a configuration option to disable Firebug Lite loading; it's automatic when no console is detected, so users might need to modify the library code to avoid this.

Does console.log-wrapper support log levels like info or error?

No, it only wraps console.log for basic logging, as stated in the features, so it lacks support for other console methods, which might require additional polyfills or libraries.

How to integrate console.log-wrapper with a build tool like Webpack?

Since it supports AMD and CommonJS, you can import it via require or import statements, but the README doesn't offer specific guidance for modern bundlers, leaving setup details to the user.

What browsers does console.log-wrapper exactly support?

It explicitly supports legacy browsers like IE7-10, iOS 5, and Opera 11, ensuring logging works even without native consoles, as detailed in the README's compatibility notes.

Open-Awesome

console.log-wrapper

ISCJavaScript

A cross-browser console.log wrapper that ensures safe, structured logging even in legacy browsers without native console support.

Visit Website GitHub

403 stars55 forks0 contributors

What is console.log-wrapper?

Console.log-wrapper is a JavaScript library that wraps console.log to provide safe, structured logging across all browsers, including legacy versions without native console support. It solves the problem of broken or missing console output in older browsers by automatically loading Firebug Lite when needed and offering enhanced readability through optional plugins.

Target Audience

Frontend developers and web developers who need reliable debugging tools across multiple browser versions, especially those supporting legacy browsers like IE7-10, iOS 5, or Opera 11.

Value Proposition

Developers choose Console.log-wrapper because it guarantees console logging works everywhere, eliminates cross-browser inconsistencies, and provides configurable, well-structured output without requiring polyfills or manual workarounds.

Overview

Clear console logging for every browser

Use Cases

Best For

Debugging JavaScript applications in legacy browsers like IE7-10
Ensuring consistent console output across all browser versions
Adding structured logging to projects with mixed browser support
Improving readability of complex objects and arrays in primitive consoles
Simplifying cross-browser development without worrying about console availability
Enhancing debugging workflows in environments with limited developer tools

Not Ideal For

Modern web applications targeting only evergreen browsers with native console support
Projects requiring server-side logging or integration with centralized log management systems
Performance-sensitive applications where loading Firebug Lite could impact page load times
Teams using TypeScript or needing strong typing for logging functions

Pros & Cons

Pros

Universal Browser Support

Automatically loads Firebug Lite for browsers without a console, ensuring logging works in legacy environments like IE7-10, as highlighted in the README's cross-browser focus.

Structured Output

Handles strings, objects, arrays, and functions with clear, organized printing, demonstrated in the demo screenshots for improved readability across data types.

Configurable Settings

Offers customization via log.settings() for line numbers and grouping, allowing developers to tailor the logging output to their debugging needs.

Optional Readability Plugin

Detail Print plugin enhances object and array display in primitive consoles like IE and older iOS, addressing limitations shown in the README's comparison images.

Cons

External Firebug Lite Dependency

Automatically loads Firebug Lite when needed, which adds external bloat and can cause compatibility or performance issues in modern setups, with no disable option mentioned.

Limited to Basic Console.log

Focuses solely on console.log without support for other console methods like warn or error, making it less suitable for comprehensive logging frameworks.

No Built-in Error Handling

The README doesn't address error scenarios or provide fallbacks if Firebug Lite fails to load, which could leave logging broken in edge cases.

Frequently Asked Questions

Related Projects

log

Console.log with style.

Stars3,007

Forks143

Last commit3 years ago

loglevel

:ledger: Minimal lightweight logging for JavaScript, adding reliable log level methods to wrap any available console.log methods

Stars2,747

Forks160

Last commit1 year ago

Conzole

Oaxoa.github.io

Stars213

Forks18

Last commit10 years ago

minilog

Lightweight client & server-side logging with Stream-API backends

Stars0

Forks0

Last commit

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub