Configurable loggers / json logging

[ematipico]

Summary

// astro.config.mjs
import { defineConfig, logHandlers } from "astro/config";

export default defineConfig({
  experimental: {
    logger: logHandlers.json({ pretty: true }),
  },
});

astro dev --json

Links

• Rendered RFC
• Stage 2 Proposal
• Stage 1 Proposal

[florian-lefebvre]

I imagine an adapter could provide something like waitUntil which doesn't block the request, otherwise block the request

[ematipico]

Possibly, but probably we can forget of the flush function. We will revisit once waitUntil lands in the next minor

[matthewp]

From the user perspective, is there any real difference between the console and node loggers? They do the same, right, one just only works in Node, in which case, why have it?

[ematipico]

They don't do the same thing.

Node.js uses stdout/stderr to print the messages.

Console prints to console via info/warn/error

[matthewp]

Console always prints to stdout/stderr though. Do you know if there's an advantage to having both? Or did you do it that way because we already had both in the codebase (which IIRC is just historical and not purposefully designed).

[ematipico]

Console always prints to stdout/stderr though

Do you mean that the runtime (Node.js, workderd, etc.) does that? If so, then it's an implementation detail.

Or did you do it that way because we already had both in the codebase (which IIRC is just historical and not purposefully designed).

Yes we do. CLI and Pipeline use two different loggers. CLI uses a node.js logger, while the pipeline uses the console logger. Additionally, I didn't exclude the idea that a user could create a client logger, so I wanted to keep things open ended for now.