From ba20823c0add1fb30ad14f0bf5c8c607a6ee851b Mon Sep 17 00:00:00 2001 From: James Ritchie Date: Wed, 7 May 2025 13:48:16 +0100 Subject: [PATCH] =?UTF-8?q?Docs:=20Adds=20Yarn=20=E2=80=98Plug=E2=80=99n?= =?UTF-8?q?=E2=80=99Play=E2=80=9D=20conflicts=20fix=20to=20troubleshooting?= =?UTF-8?q?=20page?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/troubleshooting.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/troubleshooting.mdx b/docs/troubleshooting.mdx index 40a80d9897..99ec41af38 100644 --- a/docs/troubleshooting.mdx +++ b/docs/troubleshooting.mdx @@ -34,6 +34,17 @@ sudo chown -R $(whoami) ~/.npm Ensure you have stopped your local dev server then locate the hidden `.trigger` folder in your project and delete it. You can then restart your local dev server. +### Yarn Plug'n'Play conflicts + +If you see errors like this when running `trigger.dev dev`: + +``` +Could not resolve "@trigger.dev/core/v3" +The Yarn Plug'n'Play manifest forbids importing "@trigger.dev/core" here because it's not listed as a dependency of this package +``` + +And you're using Yarn v1.22 or another package manager, check if you have a `.pnp.cjs` file in your home directory. This can happen if you previously had Yarn Plug'n'Play enabled globally. Remove the `.pnp.cjs` file to resolve the issue. + ## Deployment Running the [trigger.dev deploy] command builds and deploys your code. Sometimes there can be issues building your code.