Rom
Hm, yea, a minimal reproduction would be best. No rush. Let's re-open then.
It's logs coming from worker code. (I only mentioned the Vite startup log as a vivid example of how missing colors can degrade DX — that log *does* print in...
Hm, I see. Indeed, it seems like `FORCE_COLOR` is the only option here. `@cloudflare/vite-plugin` could (and should AFAICT) set `FORCE_COLOR` to true in dev and preview.
👍 Makes sense
Maybe a new flag `nodejs_compat_light` that is true by default would be a good compromise.
In the meantime, we implemented [this workaround](https://github.com/brillout/picocolors/commit/a56bc392d068ce5dd6fe811c1ea19e4a545e1907) on our side.
@Ercilan Have you seen https://vike.dev/onAfterRenderHtml#pagecontext-pagehtml-string-stream ? > only has the HTML inside #app. No, it does have the entire HTML. (Minus the `` and `` tags injected by Vike.)
Ah, you're right, you can't access `headHtml`. How about exposing it over `pageContext.headHtml`? Would that solve your issue?
@Ercilan Can you use the workaround mentioned [here](https://github.com/vikejs/vike/issues/1979#issue-2684032285)? > I think it’s better to provide the full HTML. That way it matches the intuitive meaning of the function name AfterRenderHtml...
https://github.com/magne4000/vite-plugin-vercel/blob/14ffa67357eb27ee425829defdaf1efda3cbde39/packages/vike/src/plugins/prerender.ts#L40-L41 ```ts type PrerenderContext = { pageContexts: PageContext[] output: Output _pageContextInit: Record | null _noExtraDir: boolean | null _prerenderedPageContexts: PrerenderedPageContexts } ```