Steven

> Using the wrong package manager for the currently installed project is broken and should be fixed upstream @arcanis I don't know how this can be fixed upstream. For example,...

How about adding something like “corepack --save [email protected]” that writes to the package.json?

> I'd prefer if users didn't have to deal with Corepack at all once they have enabled it I already have to interact with corepack `activate` to install a global...

The readme could use some improvement. Here's a shameless plug for a blog post I wrote that should answer all your questions: https://styfle.dev/blog/corepack

Also try `echo $PATH` or `echo %PATH%` which will show you the precedence of which directories are searched on your machine. As mentioned above, likely nvm path is prepended in...

Bugs and feedback can be reported at https://github.com/vercel/satori

You need Node.js 16 or newer. See the docs here https://vercel.com/docs/concepts/functions/edge-functions/og-image-generation

If you have a problem that reproduces using [the playground](https://og-playground.vercel.app), please create an issue in the [satori](https://github.com/vercel/satori) repo. For all other issues with `@vercel/og`, please reach out to [Vercel Support](https://vercel.com/help#issues).

I think this might be an actual bug but I don't have time to look into it: https://github.com/vercel/vercel/actions/runs/7846798470/job/21414416724?pr=11133#step:10:1979 ``` vercel:test: ✕ should detect update command (46 ms) vercel:test: vercel:test: ●...

Looks like this is blocked by https://github.com/vercel/vercel/pull/11405