trackly_logger 0.2.0

A lightweight, zero-dependency logger for Dart and Flutter with log levels, colored output, tags, and clickable links to the line of code that wrote each log.

trackly_logger

A lightweight, zero-dependency logger for Dart and Flutter. Colored, readable logs that tell you exactly which line of code wrote them. Click the location in VS Code or Android Studio to jump straight to it.

[2026-09-27 10:53:53.664] [DEBUG  ] 🐞 Config loaded (package:my_app/main.dart:6:11) | extra: {env: dev, retries: 3}
[2026-09-27 10:53:53.665] [SUCCESS] ✅ Connected to the server (package:my_app/main.dart:8:11)
[2026-09-27 10:53:53.665] [WARNING] ⚠️ Cache is almost full (package:my_app/main.dart:9:11)
[2026-09-27 10:53:53.666] [INFO   ] ℹ️ [CartService] Added apple (package:my_app/cart/cart_service.dart:12:40)
[2026-09-27 10:53:53.793] [DEBUG  ] 🐞 Load users took 126 ms (package:my_app/users/users_page.dart:25:31)

Features

• Seven levels: trace, debug, info, success, warning, error, fatal.
• Jump to the code: every log ends with the file, line, and column that wrote it, as a link that opens the code in VS Code and Android Studio.
• Colors, emojis, and timestamps, each of which can be turned off.
• Tags: per-feature loggers, or the class name through a mixin.
• Errors, stack traces, and extra data on any log.
• Timing: measure() logs how long an operation took.
• Off in release builds by default.
• Outputs: console, Dart DevTools, in-memory history, or your own (e.g. Crashlytics).
• No dependencies. Works on every platform Dart and Flutter support.

Installation

flutter pub add trackly_logger
# or, for Dart projects:
dart pub add trackly_logger

Usage

import 'package:trackly_logger/trackly_logger.dart';

trackly.trace('Reading config');
trackly.debug('Config loaded', extra: {'env': 'dev'});
trackly.info('App started');
trackly.success('Signed in');
trackly.warning('Cache is almost full');
trackly.fatal('Out of memory');

try {
  await api.fetchUsers();
} catch (e, st) {
  trackly.error('Failed to load users', error: e, stackTrace: st);
}

Tagged loggers

Create a logger with a tag to see which part of the app a log came from:

const network = TracklyLogger('Network');
network.info('GET /users'); // [INFO   ] ℹ️ [Network] GET /users

Or add TracklyLoggerMixin to a class to get a logger tagged with the class name:

class CartService with TracklyLoggerMixin {
  void addItem(String id) => logger.info('Added $id');
  // [INFO   ] ℹ️ [CartService] Added apple
}

Class names are shortened when code is obfuscated. Override loggerTag to keep them readable:

@override
String get loggerTag => 'CartService';

Timing

measure() runs a function, logs how long it took, and returns its result. If the function throws, it logs the error and rethrows it.

final users = await trackly.measure('Load users', api.fetchUsers);
// [DEBUG  ] 🐞 Load users took 126 ms [users_page.dart:24]

Lazy messages

Pass a function to build a message only when it will actually be logged:

trackly.debug(() => 'State: ${state.toJson()}');

Configuration

All loggers share these settings:

// On by default, except in release builds.
TracklyLogger.enabled = true;

// Ignore anything below this level.
TracklyLogger.minLevel = TracklyLevel.info;

// Turn off the code location to skip capturing a stack trace per log.
TracklyLogger.showCaller = false;

// Drop specific records, e.g. mute a noisy tag.
TracklyLogger.filter = (record) => record.tag != 'Network';

// Change how logs are printed.
TracklyLogger.output = const TracklyConsoleOutput(
  colors: true, // Default: on, except on iOS.
  emojis: true,
  timestamp: true,
  callerLinks: true, // false shows `main.dart:6` instead of a full link.
  maxLineLength: 800, // Longer lines are split so logcat doesn't cut them.
);

Colors are off by default on iOS, because iOS logs show the color codes as text, such as \^[[34m. If your console shows codes like [33m elsewhere, use TracklyConsoleOutput(colors: false).

Outputs

Output	Sends logs to
TracklyConsoleOutput	The console, using print (the default).
TracklyDeveloperOutput	The Logging tab of Dart & Flutter DevTools, via dart:developer.
TracklyMemoryOutput	An in-memory list of recent records, for an in-app log viewer or bug reports.
TracklyMultiOutput	Several outputs at once.

final history = TracklyMemoryOutput(capacity: 200);

TracklyLogger.output = TracklyMultiOutput([
  const TracklyConsoleOutput(),
  const TracklyDeveloperOutput(),
  history,
]);

// Later, e.g. when the user sends feedback:
final report = history.records
    .expand(const TracklyConsoleOutput(colors: false).format)
    .join('\n');

Custom outputs

Extend TracklyOutput to send logs anywhere. For example, to report errors to Firebase Crashlytics in release builds:

class CrashlyticsOutput extends TracklyOutput {
  @override
  void write(TracklyRecord record) {
    if (record.level >= TracklyLevel.error) {
      FirebaseCrashlytics.instance.recordError(
        record.error ?? record.message,
        record.stackTrace,
        reason: record.message,
      );
    }
  }
}

void main() {
  TracklyLogger.enabled = true; // Keep logging on in release.
  TracklyLogger.output = TracklyMultiOutput([
    if (kDebugMode) const TracklyConsoleOutput(),
    CrashlyticsOutput(),
  ]);
  runApp(const MyApp());
}

Logging uncaught Flutter errors

void main() {
  FlutterError.onError = (details) {
    trackly.fatal(
      details.exceptionAsString(),
      error: details.exception,
      stackTrace: details.stack,
    );
  };
  PlatformDispatcher.instance.onError = (error, stackTrace) {
    trackly.fatal('Uncaught error', error: error, stackTrace: stackTrace);
    return true;
  };
  runApp(const MyApp());
}

Jump to the code

Every log ends with where it was written, such as (package:my_app/auth/login_page.dart:42:7). IDEs turn this into a link to that line:

Where you read the logs	Click the location
VS Code Debug Console (run with F5)	✓
VS Code terminal (flutter run)	✓
Android Studio / IntelliJ Run console	✓
A plain terminal or Xcode	Shown, not clickable

VS Code needs the Dart extension, and Android Studio needs the Flutter or Dart plugin. Both are installed with Flutter support.

The location is read from the stack trace, so it's available wherever Dart produces readable stack traces, such as Flutter apps in debug mode and Dart CLI and server apps. When stack traces aren't readable, for example on the web or in builds using --obfuscate or --split-debug-info, it's left out and everything else still works.

Your own outputs get it as record.location, with the uri, line, and column, and the clickable link.

License

MIT. See LICENSE.