Sam Ko
Hi everyone, was investigating this— The [PR](https://github.com/vercel/next.js/pull/70256) that is causing this issue for Azure and Cloud Run (as far as I'm aware) is because both platforms are (I don't see...
@2chanhaeng Thank you for sharing! The team has been made aware of this issue—we are taking a look!
@jmikrut Not running into this error myself ``` 68805-turbopack-serverExternalPackages [main] p devturbo > [email protected] devturbo /.../68805-turbopack-serverExternalPackages > pnpm dev --turbo > [email protected] dev /.../68805-turbopack-serverExternalPackages > cross-env NODE_OPTIONS="${NODE_OPTIONS} --no-deprecation" next dev...
@jmikrut It seems error out because I don't have the correct keys. Where do I should I go create my keys (ideally, a shouldn't require this step)?
Hmm, it seems to not just be that package. ``` ⨯ ./node_modules/.pnpm/@[email protected]/node_modules/@libsql/client/lib-esm/node.js Package @libsql/client (serverExternalPackages or default list) can't be external The request @libsql/client matches serverExternalPackages (or the default list),...
Good news, it was already reported internally—we are taking a look!
@khuezy what version were you using before?
@sannajammeh Taking a look—
@sannajammeh Can confirm this is a bug, and the team has been aware. This only occurs when dynamic importing a Client Component → Server Component. It is properly code-split when...
@l0gicgate The CodeSandbox refuses to load, not sure why. Is it possible to move the to a public GitHub repo instead?