| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-07-16 | 1.1 kB | |
| v5.1.0 source code.tar.gz | 2026-07-16 | 877.4 kB | |
| v5.1.0 source code.zip | 2026-07-16 | 1.0 MB | |
| Totals: 3 Items | 1.9 MB | 1 | |
Added
- Named sub-loggers on
tslog/lite—LiteLoggergainsname/nameSeparatoroptions andgetSubLogger()/child(). The label is partially applied withFunction.prototype.bind, so a sub-logger's level methods are still the bound nativeconsole.*functions and the devtools file:line badge keeps pointing at the caller. Every%in a label is escaped so a (possibly runtime-derived) name can never act as a console format specifier and consume a logged value. Sub-loggers nest to any depth, join names with the parent'snameSeparator(default":"), and inheritminLeveland the sink unless overridden; an unresolvableminLeveloverride inherits the parent's level, matching the fullLogger. Known trade-off (documented): on a named lite logger the label occupies the console's format-string slot, so printf-style specifiers in messages print literally. - Bundle-size budget for
tslog/lite—check-bundle-sizenow probes the lite subpath (~0.8 KB gzip measured, 1 KB budget).
https://github.com/fullstack-build/tslog/compare/v5.0.2...v5.1.0