Matt Kane
Matt Kane
Setting `process.env.FORCE_COLOR` works for `picocolors`. The problem for `chalk` is that `process.stdout` is *not* a TTY in workerd, so it won't report as such.
Yes, I think that would be a good idea for dev at least. What do you think, @jamesopstad?
> This is harder than I hoped because `picocolors` doesn't read `FORCE_COLOR` from `process.env.FORCE_COLOR` but instead stores `process.env` in an `env` variable first: > > https://github.com/alexeyraspopov/picocolors/blob/0e7c4af2de299dd7bc5916f2bddd151fa2f66740/picocolors.js#L4 > > This means...
I'm not going to merge this as it will break links without good reason
@petebacondarwin Can this be closed now that it uses the OpenNext template?
Could you create a reproduction? Easiest is if you use https://astro.new/repro/
When I tried this locally, with a new project, I got "✘ [ERROR] The entry-point file at ".open-next/worker.js" was not found.". I needed to do another `npm run deploy` manually
The issue is that it doesn't run `opennextjs-cloudflare build`. I'm not sure what the best workaround is here.
Should it change the build command?
> 0927724e423551ea8949ce028da556626ddb3032 I think these changes should be in a separate PR. Will they then override the package.json build command too?