Lennart

No, haven't tried 2.7.3 yet! > Does gatsby use/open any of the same databases that parcel uses No, I don't think so. We use Parcel's LMDBCache (https://github.com/gatsbyjs/gatsby/blob/204825250ca302a73e1ce695222ec29b96112782/packages/gatsby/src/utils/parcel/compile-gatsby-files.ts#L111-L112) but that shouldn't...

This should be fixed by https://github.com/clerk/javascript/pull/3326 and was published with `@clerk/[email protected]`. Please install the latest version of `@clerk/clerk-expo` in order to fix your issue: ```shell npm install @clerk/clerk-expo@latest ```

Closing for now and will revisit this in the new year

Hi! With https://github.com/gatsbyjs/gatsby/pull/37449 merged there won't be a need anymore for this workaround using an API we don't really want people to use. It'll be released in Gatsby 5.5

Closing as stale for now

Closing out as stale

Closing for now as it's not actionable at the moment. We can re-open once it's decided in https://github.com/netlify/next-runtime/issues/1475 that Next.js has upgraded their Node.js requirements

Hi! Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a [minimal reproduction][reproduction]....

You can install from GitHub so long, (e.g. with pnpm https://pnpm.io/cli/add#install-from-git-repository). Or use https://www.npmjs.com/package/patch-package I created a fork and added a `prepare` script so that the package gets built: https://github.com/LekoArts/consola/tree/prepare-script...

Hi! Sorry to hear you're running into an issue. To help us best begin debugging the underlying cause, it is incredibly helpful if you're able to create a [minimal reproduction][reproduction]....