logkeeper 1.3.0

Simple file logger that works out of the box with automatic timestamping and session management.

Changelog

1.0.0

• Initial version.

1.0.0+1

• Updated documentation.

1.1.0

✨ New Features (All 100% Optional)

This release adds several optional configuration options that improve flexibility while keeping LogKeeper’s original zero-configuration philosophy completely intact.
If no configuration is provided, LogKeeper continues to work exactly as before.

• Added optional configuration method LogKeeper.configure():

  • logDirectory: Custom directory for log files (default: cwd/logs)
  • minLevelForProduction: Minimum log level for production (default: LogLevel.info)
  • fileNameDateFormat: Custom date format for log file names (default: yyyy-MM-dd_HH-mm-ss)
  • timestampFormat: Custom date format for log message timestamps (default: Hms())
  • maxLogAgeDays: Automatically deletes old log files older than N days (default: disabled)
  • writeToFileInDevMode: Whether to also write logs to file in development mode (default: false)

• Added automatic console output:

  • In development mode, LogKeeper now writes logs to the console by default.
  • In production mode, logs are written only to file (no console output).

🧱 Still Zero Configuration

If you simply call:

LogKeeper.info('App started');
await LogKeeper.saveLogs();

Everything will work exactly the same as in previous versions — no configuration required.

1.1.0+1

• Updated documentation.

1.1.0+2

• Unnecessary public method removed

1.1.1

Fix

• Fixed unnecessary .log file creation in development mode

1.2.0

Added

• colorizeConsoleOutput: Colorized console output for better log readability
  • Log levels now have distinct colors for easier visual identification
  • Colors can be disabled via configuration option

1.3.0

Fix

• Resolved FileSystemException: Creation failed, path = 'logs' (OS Error: Read-only file system, errno = 30) on Android and other environments where the process working directory is not writable. The default log directory is now created under the application support directory from path_provider instead of a relative logs folder next to the current working directory.

Added

• LogKeeper.logDirectoryPath: read-only getter that returns the absolute directory where log files are written. It is null until a custom directory is set with configure, or until ensureLogDirectoryPath or the first log write initializes the default support-directory logs folder.
• LogKeeper.ensureLogDirectoryPath(): returns a Future<String> with that same absolute path and guarantees initialization (including the internal file manager) without requiring a prior log call. Prefer this when you need a non-null path before any logging.