Releases: VersaLog/VersaLog.js
Releases · VersaLog/VersaLog.js
V2.1.0
Overview
This PR introduces a plugin-based architecture and removes direct dependencies on external notification libraries.
Changes
- Removed
node-notifierfrom core to improve security and reduce dependencies - Added
setNotifier()API to allow external notification plugins - Refactored logging output to use
process.stdout.writefor better performance - Improved module exports for better TypeScript / ESM compatibility
- Cleaned up unused dependencies
Breaking Changes
- Removed built-in notification support (
node-notifier) - Users must now provide a notifier via plugin if needed
Example
import VersaLog from "versalog"
import { notifyPlugin } from "versalog/plugin/notify"
const log = new VersaLog()
notifyPlugin(log)
log.error("Test error")Motivation
- Resolve indirect dependency vulnerabilities (uuid via node-notifier)
- Reduce bundle size and improve maintainability
- Provide a more flexible and extensible architecture
Notes
This is a breaking change, so version bump to v2.1.0 is recommended.
🌸 V2.0.0 Spring Update: Progress Logging
Summary
This Spring Update brings more visibility and "aliveness" to VersaLog. We’ve introduced Progress Logging to eliminate the guesswork during long-running tasks and batch executions.
No more staring at static INFO logs—now you can see exactly how far your processes have come and how much longer they’ll take.
V1.7.2
V1.6.5: Merge pull request #7 from VersaLog/all-contributors/add-yomi4486
docs: add yomi4486 as a contributor for code