Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update serverExternalPackages for next dev --turbo #7628

Closed
christianfullstack opened this issue Aug 12, 2024 · 3 comments
Closed

Update serverExternalPackages for next dev --turbo #7628

christianfullstack opened this issue Aug 12, 2024 · 3 comments
Assignees

Comments

@christianfullstack
Copy link

Link to reproduction

No response

Payload Version

v3.0.0-beta.77

Node Version

v20.9.0

Next.js Version

tested with current ^15.0.0-canary.111 and ^15.0.0-canary.104

Describe the Bug

While executing next dev --turbo i get following Error:
but this is just in the turbo Mode.

`⨯ ./node_modules/.pnpm/mongodb@4.17.1_@aws-sdk+client-sso-oidc@3.598.0/node_modules/mongodb/lib/index.js
Package mongodb (serverExternalPackages or default list) can't be external
The request mongodb matches serverExternalPackages (or the default list), but it can't be external:
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install the package into the project directory.

./node_modules/.pnpm/mongoose@6.12.3_@aws-sdk+client-sso-oidc@3.598.0/node_modules/mongoose/index.js
Package mongoose (serverExternalPackages or default list) can't be external
The request mongoose matches serverExternalPackages (or the default list), but it can't be external:
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install the package into the project directory.

./node_modules/.pnpm/pino@9.3.1/node_modules/pino/pino.js
Package pino (serverExternalPackages or default list) can't be external
The request pino matches serverExternalPackages (or the default list), but it can't be external:
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install the package into the project directory.

./node_modules/.pnpm/pino-pretty@11.2.1/node_modules/pino-pretty/index.js
Package pino-pretty (serverExternalPackages or default list) can't be external
The request pino-pretty matches serverExternalPackages (or the default list), but it can't be external:
The request could not be resolved by Node.js from the project directory.
Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.
Try to install the package into the project directory.
`

Reproduction Steps

execute next dev --turbo

Adapters and Plugins

No response

@christianfullstack christianfullstack added status: needs-triage Possible bug which hasn't been reproduced yet v3 labels Aug 12, 2024
@neslob
Copy link

neslob commented Aug 12, 2024

I have the same issue with these versions.

    "@lexical/headless": "0.17.0",
    "@lexical/html": "0.17.0",
    "@lexical/link": "0.17.0",
    "@lexical/list": "0.17.0",
    "@lexical/mark": "0.17.0",
    "@lexical/markdown": "0.17.0",
    "@lexical/react": "0.17.0",
    "@lexical/rich-text": "0.17.0",
    "@lexical/selection": "0.17.0",
    "@lexical/utils": "0.17.0",
    "@payloadcms/db-postgres": "3.0.0-beta.77",
    "@payloadcms/email-nodemailer": "3.0.0-beta.77",
    "@payloadcms/next": "3.0.0-beta.77",
    "@payloadcms/plugin-cloud": "3.0.0-beta.77",
    "@payloadcms/richtext-lexical": "3.0.0-beta.77",
    "@payloadcms/storage-s3": "3.0.0-beta.77",
    "@payloadcms/ui": "3.0.0-beta.77",
    "next": "15.0.0-canary.104",
    "react": "19.0.0-rc-06d0b89e-20240801",
    "react-dom": "19.0.0-rc-06d0b89e-20240801",

@github-actions github-actions bot removed the status: needs-triage Possible bug which hasn't been reproduced yet label Aug 12, 2024
@jmikrut
Copy link
Member

jmikrut commented Aug 12, 2024

Hey all, this broke with Next.js and I opened an issue to track here:

vercel/next.js#68805

Let's consolidate feedback on that issue!

@jmikrut jmikrut closed this as completed Aug 12, 2024
Copy link

github-actions bot commented Sep 6, 2024

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants