48 stable releases

new 2024.11.135 Nov 18, 2024
2024.10.132 Oct 28, 2024
2024.7.110 Jul 29, 2024
2024.3.91 Mar 25, 2024
0.1.1 May 3, 2017

#19 in Games

Download history 231/week @ 2024-07-27 326/week @ 2024-08-03 240/week @ 2024-08-10 249/week @ 2024-08-17 154/week @ 2024-08-24 10/week @ 2024-08-31 115/week @ 2024-09-07 156/week @ 2024-09-14 227/week @ 2024-09-21 286/week @ 2024-09-28 158/week @ 2024-10-05 188/week @ 2024-10-12 14/week @ 2024-10-19 127/week @ 2024-10-26 125/week @ 2024-11-02 14/week @ 2024-11-09

288 downloads per month

MIT license

37KB
1K SLoC

retro

Retro game catalog management.

Development

Logging

Logs can be emitted at the following levels: error, warn, info, and debug. When each level is sent to stdout depends on the log level specified when invoking retro.

error logs are sent to stdout by default. These should be used anytime the command takes an action (e.g., a symlink is created). This includes dry runs of commands. They should also be used to report actual errors.

warn logs should be used when an action is skipped (e.g., a symlink already exists). They should also be used to report a summary of output that is normally streamed from an underlying command.

info logs should be used to indicate that no action was attempted (e.g., a system is not configured).

debug logs should be used sparingly as there may be dependencies that use this level of logging.

Dependencies

~4–15MB
~141K SLoC