A lightweight wrapper for all console methods that automatically suppresses output in production environments and supports optional tag-based filtering in development.
npm install @onamfc/developer-logImport and use just like you would use the native console object:
import{dev}from'@onamfc/developer-log';// Basic loggingdev.log('Hello, world!');dev.error('An error occurred');dev.warn('This is a warning');dev.info('Informational message');dev.debug('Debug information');// Logging with tags for filtering (optional)dev.log('Database connected',{tag: 'database'});dev.error('API request failed',error,{tag: 'api'});dev.warn('Cache miss',cacheKey,{tag: 'cache'});// Advanced methodsdev.table([{name: 'John',age: 30},{name: 'Jane',age: 25}]);dev.trace('Stack trace');dev.dir({foo: 'bar'});// Groupingdev.group('My Group');dev.log('Inside group');dev.groupEnd();dev.groupCollapsed('Collapsed Group');dev.log('Hidden by default');dev.groupEnd();// Timingdev.time('operation');// ... your code ...dev.timeEnd('operation');dev.timeLog('operation','Checkpoint');// Countingdev.count('clicks');dev.count('clicks');dev.countReset('clicks');// Assertionsdev.assert(value===expected,'Values do not match');// Other methodsdev.clear();dev.dirxml(document.body);You can also use the default export:
importdevfrom'@onamfc/developer-log';dev.log('Using default export');The package checks process.env.NODE_ENV and suppresses all output when it equals 'production'. In all other environments (development, test, etc.), it behaves exactly like the native console methods.
Control which logs are displayed during development using optional tags. This is useful for filtering logs by category, feature, or component.
Option 1: Auto-Load (Recommended)
Simply create a config file in your project root with one of these names:
dev-log.config.json.devlogrc.json.devlogrc
The config file will be automatically loaded when the module is imported (in non-production environments only).
{
"disabledTags": ["verbose", "debug", "trace"]
}No additional code needed - just import and use:
import{dev}from'@onamfc/developer-log';// Config already loaded automatically!// All tags show except those in disabledTagsdev.log('Query executed',{tag: 'database'});// Showsdev.log('Verbose details',{tag: 'verbose'});// HiddenOption 2: Programmatic Configuration
For dynamic configuration or when you need to set tags based on runtime conditions:
import{dev}from'@onamfc/developer-log';// Hide specific tags, show everything elsedev.configure({disabledTags: ['verbose','debug','trace']});Where to place dev.configure():
- In your main entry point (
index.ts,app.ts,server.ts,main.ts) - Before any code that uses tagged logs
- In framework initialization:
- Express/Node.js: Top of your main server file
- Next.js: In
_app.tsxorlayout.tsx - React: In
index.tsxorApp.tsx - NestJS: In
main.tsbeforeapp.listen()
Option 3: Explicit File Loading
Load a config file from a specific path:
import{dev}from'@onamfc/developer-log';dev.loadConfig('./config/dev-log.config.json');Config File Format:
{
"disabledTags": ["verbose", "debug", "trace"]
}All tags are shown by default. Only tags in disabledTags will be hidden.
Configuration Priority:
If multiple configuration methods are used, the last one wins:
- Auto-loaded config (happens first, at module import)
- Programmatic
dev.configure()(overrides auto-loaded config) - Explicit
dev.loadConfig()(overrides everything)
Add a tag by passing an options object as the last parameter:
// Tagged logs - only show if tag is enableddev.log('Database query executed',result,{tag: 'database'});dev.error('API request failed',error,{tag: 'api'});dev.warn('Authentication timeout',{tag: 'auth'});// Untagged logs - always show regardless of configurationdev.log('Application started');dev.error('Critical error occurred',error);- No configuration: All logs (tagged and untagged) are displayed
- With
disabledTags: All logs except those with disabled tags are displayed - Untagged logs: Always displayed regardless of configuration
- Production environment: All logs are suppressed (tags have no effect)
Scenario 1: Hiding noisy logs
// You have lots of verbose logs that clutter your consoledev.log('Verbose cache details',data,{tag: 'verbose'});dev.log('Debug information',{tag: 'debug'});dev.log('Trace data',{tag: 'trace'});dev.log('User logged in',{tag: 'auth'});// Important log// Hide the noisy tags, but keep everything elsedev.configure({disabledTags: ['verbose','debug','trace']});// Now: auth and all other logs show, but verbose/debug/trace are hiddenScenario 2: Production-like logging in development
// Disable development-only debug logsdev.log('SQL Query: SELECT * FROM users',{tag: 'sql-debug'});dev.log('Cache hit ratio: 85%',{tag: 'performance-debug'});dev.error('Payment failed',error,{tag: 'payment'});// Important// Simulate production loggingdev.configure({disabledTags: ['sql-debug','performance-debug']});// Only important logs show, like productionScenario 3: Dynamic configuration via environment
// In your main app entry pointif(process.env.DISABLE_TAGS){dev.configure({disabledTags: process.env.DISABLE_TAGS.split(',')});}// Run with: DISABLE_TAGS=verbose,debug npm start// All logs show except verbose and debugAll standard console methods are supported:
log- General loggingerror- Error messageswarn- Warning messagesinfo- Informational messagesdebug- Debug messagestrace- Stack tracetable- Tabular datadir- Object inspectiondirxml- XML/HTML element inspectiongroup- Create a message groupgroupCollapsed- Create a collapsed message groupgroupEnd- End a message groupclear- Clear the consolecount- Count occurrencescountReset- Reset counterassert- Assertion testingtime- Start a timertimeEnd- End a timertimeLog- Log elapsed time
- Clean production builds: No need to manually remove debug statements
- Granular log control: Filter logs by category/feature using tags during development
- Reduce noise: Focus on relevant logs without commenting out code
- Type-safe: Full TypeScript support
- Zero dependencies: Lightweight and efficient
- Drop-in replacement: Works exactly like
consolein development - Performance: No overhead in production (all methods are no-ops)
- Flexible filtering: Configure via code or config file
Simply replace console with dev:
// Beforeconsole.log('Debug message');console.error('Error message');console.table(data);// Afterimport{dev}from'@onamfc/developer-log';dev.log('Debug message');dev.error('Error message');dev.table(data);Optional: Add tags for better log organization
// After migration, optionally add tagsdev.log('User authenticated',user,{tag: 'auth'});dev.log('Verbose trace data',data,{tag: 'verbose'});dev.warn('Debug information',{tag: 'debug'});// Hide noisy tags to clean up your consoledev.configure({disabledTags: ['verbose','debug']});// Now 'verbose' and 'debug' logs are hidden, everything else showsFull support for all features including:
- ✅ Tag-based filtering
- ✅ Auto-load config from files
- ✅ Programmatic configuration
- ✅ File-based configuration with
loadConfig()
Basic logging works perfectly, with some limitations:
- ✅ All console methods work (log, error, warn, etc.)
- ✅ Tag-based filtering with programmatic configuration
- ✅ Production environment suppression
- ❌ Auto-load config files (Node.js file system not available)
- ❌
dev.loadConfig()(Node.js file system not available)
React Native Usage:
import{dev}from'@onamfc/developer-log';// Use programmatic configuration instead of file-baseddev.configure({disabledTags: ['verbose','debug']});// Everything else works the samedev.log('User logged in',{tag: 'auth'});// Showsdev.log('Verbose details',{tag: 'verbose'});// Hiddendev.error('API error',error,{tag: 'api'});// ShowsThis package is written in TypeScript and includes type definitions out of the box.
MIT