Files
bsky-social-app/src/logger
Samuel Newman bc072570d2 Activity notification settings (#8485)
Co-authored-by: Eric Bailey <git@esb.lol>
Co-authored-by: Samuel Newman <mozzius@protonmail.com>
Co-authored-by: hailey <me@haileyok.com>
2025-07-01 14:36:04 -07:00
..
2025-02-28 12:09:36 -06:00
2025-02-28 12:09:36 -06:00
2025-06-11 13:22:02 -05:00
2025-02-28 12:09:36 -06:00

Logger

Simple logger for Bluesky.

At a Glance

import { logger, Logger } from '#/logger'

// or, optionally create new instance with custom context
// const logger = Logger.create(Logger.Context.Notifications)

// for dev-only logs
logger.debug(message, {})

// for production breadcrumbs
logger.info(message, {})

// seldom used, prefer `info`
logger.log(message, {})

// for non-error issues to look into, seldom used, prefer `error`
logger.warn(message, {})

// for known errors without an exception, use a string
logger.error(`known error`, {})

// for unknown exceptions
try {
} catch (e) {
  logger.error(e, {message: `explain error`}])
}

Log Levels

Log level defaults to info. You can set this via the EXPO_PUBLIC_LOG_LEVEL env var in .env.local.

Filtering debugs by context

Debug logs are dev-only, and not enabled by default. Once enabled, they can get noisy. So you can filter them by setting the EXPO_PUBLIC_LOG_DEBUG env var e.g. EXPO_PUBLIC_LOG_DEBUG=notifications. These values can be comma-separated and include wildcards.