
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
@skierkowski/logger
Advanced tools
Simple logging library with pretty formatting in development and JSONL in production
A simple logging library with pretty formatting in development and JSONL in production.
yarn add @skierkowski/logger
Note: This is an ESM-only module. It requires Node.js 14+ and must be imported using ES module syntax (
import
).
import { logger } from "@skierkowski/logger";
logger.info("Application started");
logger.warn("This is a warning");
logger.error("Something went wrong");
Note: Works with both ES6 modules (
import
) and CommonJS (require
).
import { info, success, warn, error } from "@skierkowski/logger";
info("Application started");
success("Operation completed successfully");
warn("This is a warning");
error("Something went wrong");
import { Logger } from "@skierkowski/logger";
const customLogger = new Logger({
level: "DEBUG",
pretty: true,
timestamp: true,
id: "API",
});
customLogger.debug("Debug message");
import { Logger } from "@skierkowski/logger";
// Create loggers for different services
const dbLogger = new Logger({ id: "DB" });
const apiLogger = new Logger({ id: "API" });
const authLogger = new Logger({ id: "AUTH" });
dbLogger.info("Database connection established");
apiLogger.warn("Rate limit exceeded");
authLogger.error("Authentication failed");
import { logger } from "@skierkowski/logger";
logger.info("User logged in", {
userId: "12345",
email: "user@example.com",
timestamp: Date.now(),
preferences: {
theme: "dark",
notifications: true,
},
});
import { logger } from "@skierkowski/logger";
try {
// Some risky operation
JSON.parse("invalid json");
} catch (err) {
// Log error directly - includes stack trace and error details
logger.error(err);
// Add additional context
logger.error(err, {
operation: "JSON parsing",
userId: "12345",
retryAttempt: 3,
});
}
When logging error objects without a configured prefix, the error type automatically becomes the prefix:
const logger = new Logger(); // No prefix configured
logger.error(new Error('Something failed')); // → "Error: Something failed"
logger.error(new TypeError('Type mismatch')); // → "TypeError: Type mismatch"
logger.error(new SyntaxError('Invalid syntax')); // → "SyntaxError: Invalid syntax"
// With configured prefix, it takes precedence
const appLogger = new Logger({ id: 'APP' });
appLogger.error(new Error('Failed')); // → "APP: Failed"
level
: Log level ('DEBUG' | 'INFO' | 'SUCCESS' | 'WARN' | 'ERROR')pretty
: Enable pretty formatting (default: true
in development, false
in production)timestamp
: Include timestamps (default: true
)id
: Service/component identifier (optional, appears white & bold in pretty mode)2025-08-03 12:00:00.123 INFO API: User logged in
userId: '12345'
email: user@example.com
preferences:
theme: dark
notifications: true
2025-08-03 12:00:01.456 SUCCESS API: Database backup completed
2025-08-03 12:00:02.123 WARN API: Rate limit warning
2025-08-03 12:00:02.789 ERROR DB: Connection failed
{"level":"INFO","message":"Application started","timestamp":"2023-08-03T12:00:00.000Z","id":"API"}
{"level":"WARN","message":"This is a warning","timestamp":"2023-08-03T12:00:01.000Z","id":"API"}
{"level":"ERROR","message":"Something went wrong","timestamp":"2023-08-03T12:00:02.000Z","id":"DB"}
The repository includes comprehensive examples showing various usage patterns:
# Run all examples
yarn examples
# Or run individual examples
yarn examples:basic # Basic usage patterns
yarn examples:levels # Log level filtering
yarn examples:services # Service ID usage
yarn examples:metadata # Metadata formatting
yarn examples:production # Development vs production modes
yarn examples:errors # Error object handling
See the examples/
directory for detailed examples and documentation.
Note: Examples use ES6 import syntax with
.js
files (enabled by a localpackage.json
in the examples directory) while maintaining full CommonJS compatibility for the main library.
# Install dependencies
yarn install
# Build the library
yarn build
# Clean build artifacts
yarn clean
FAQs
Simple logging library with pretty formatting in development and JSONL in production
We found that @skierkowski/logger demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.