You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/troubleshooting.mdx
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,17 @@ sudo chown -R $(whoami) ~/.npm
34
34
35
35
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.
36
36
37
+
### Yarn Plug'n'Play conflicts
38
+
39
+
If you see errors like this when running `trigger.dev dev`:
40
+
41
+
```
42
+
Could not resolve "@trigger.dev/core/v3"
43
+
The Yarn Plug'n'Play manifest forbids importing "@trigger.dev/core" here because it's not listed as a dependency of this package
44
+
```
45
+
46
+
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.
47
+
37
48
## Deployment
38
49
39
50
Running the [trigger.dev deploy] command builds and deploys your code. Sometimes there can be issues building your code.
0 commit comments