imccyu
2c85c484d3
1504 hand-written ranges pointing at workspace members become workspace:^, so pnpm pack substitutes each member's real version at publication: sibling peerDependencies follow the family version instead of being pinned at ^0.0.1, and a reference to a vendored package follows that package's own line. Without this, publishing 0.0.2 ships peer ranges naming a version that does not exist, and 0.0.1-rc.1 does not satisfy ^0.0.1 either. It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6 for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0. workspace:* stays where an exact published version is the point, which is how the Landlock entry pins its platform packages. A workspace constraint now requires the protocol, so a new package cannot reintroduce a hand-written range. The same constraint caught packages/boot/cmdline arriving on master without the publishable trio, which this change completes.
@cordisjs/plugin-logger-console
Console exporter for the built-in Cordis logger service.
Usage
import { Context } from 'cordis'
import ConsoleLogger from '@cordisjs/plugin-logger-console'
const root = new Context()
await root.plugin(ConsoleLogger, {
showDiff: true,
levels: {
default: 2,
hmr: 3,
},
})
root.logger('app').info('started')
Config
| Field | Description |
|---|---|
colors |
Color support level, or false to disable colors. |
maxLength |
Maximum rendered line length before truncation. |
levels |
Per-logger minimum level map. |
showDiff |
Show elapsed time since the previous message. |
showTime |
Timestamp template. |
label |
Label width, margin, and alignment options. |
The Node entry uses node:util.inspect for %o and %O; the browser entry
passes log arguments through to console.