Steven

It turns out that fetching the package.json is actually the slowest part so there was an in memory cache added here: - https://github.com/styfle/packagephobia/pull/1026 ``` fetchJSON: 627.704ms findOne (redis): 18.767ms findAll...

You could try to configure the cache directory to use .vercel/cache/11ty instead.

@murtuzaalisurti See this cachePattern here https://github.com/vercel/vercel/blob/fe6c09813a2f59b68e496172aa65462a46c12469/packages/frameworks/src/frameworks.ts#L415

Correct. Cache is ephemeral. It could expire or it could be ignored because of a change to Node.js version or many other reasons. That said it is either all or...

Thanks for working on this! I'm running CI again. Can you also update the PR title and description?

It’s probably fine to change it but it won’t make a difference since the console.warn() function is an alias for console.error() https://nodejs.org/api/console.html#consolewarndata-args

> Can you double check, @styfle that this link works for every version from our Dropdown selector? @ovflowd I confirmed that all links work 👍 However, a few old releases...

In that case, I would set the debug environment variable (`DEBUG=corepack`) to enable verbose logs.

Corepack seems to be in an odd position because the world has changed since it was first introduced: - yarn can set the project's version https://yarnpkg.com/cli/set/version - pnpm can set...