-
|
I deleted a workspace from my pnpm Turborepo project, but now whenever I run any I searched my entire project for references to the |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 4 replies
-
|
🤔 Have you re-installed with your package manager to make sure node_modules is correct? If this doesn't help, could you open an issue with reproduction steps? |
Beta Was this translation helpful? Give feedback.
-
|
Got the same issue with a renamed package. Downgrading to 1.12.2 helped. |
Beta Was this translation helpful? Give feedback.
-
|
Got the same issue with a renamed package. Version: 1.12.2 |
Beta Was this translation helpful? Give feedback.
-
|
Deleting node_modules and reinstalling turbo solved problem for me. |
Beta Was this translation helpful? Give feedback.
-
|
I was finally able to fix this. I found some documentation that I can't find again that mentioned not putting internal monorepo dependencies inside the package.json at the top level of the repo. I checked and sure enough, at some point I had added some internal dependencies there. Removing them and rerunning Given how obscure this bug was and difficult to track down, I think there should be some checks in turborepo that warn people who put internal dependencies at the top level. @anthonyshew |
Beta Was this translation helpful? Give feedback.
-
|
Interesting. In my case everything was installed internally where it was meant to be, and I still got this error. Only downgrading to 1.12.2 helped. |
Beta Was this translation helpful? Give feedback.
-
|
It is possible that downgrading to 1.12.2 wasn't what enabled turbo to work. It is possible that something in its cache gets reset when a new version is installed. |
Beta Was this translation helpful? Give feedback.
-
|
We're thinking this has more to do with our daemon. We're looking into it. |
Beta Was this translation helpful? Give feedback.
-
|
that doesn't fix my case. My project uses yarn as well |
Beta Was this translation helpful? Give feedback.
-
|
I solved this by deleting my folder and re cloning
…On Sun, Feb 4, 2024 at 1:15 AM Ben Kass ***@***.***> wrote:
It is possible that downgrading to 1.12.2 wasn't what enabled turbo to
work. It is possible that something in its cache gets reset when a new
version is installed.
—
Reply to this email directly, view it on GitHub
<#7186 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEWC4BVXPAQC46M6HQZCGDYR3HKLAVCNFSM6AAAAABCSMFBVCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGNJXG44DI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I tried everything from deleting node modules to downgrading turborepo version. Nothing is working properly for me |
Beta Was this translation helpful? Give feedback.
I was finally able to fix this. I found some documentation that I can't find again that mentioned not putting internal monorepo dependencies inside the package.json at the top level of the repo. I checked and sure enough, at some point I had added some internal dependencies there. Removing them and rerunning
pnpm installfixed the issue for me. I am not sure what the linkage is between this mistake on my part and the issue I was encountering- some kind of caching thing?Given how obscure this bug was and difficult to track down, I think there should be some checks in turborepo that warn people who put internal dependencies at the top level. @anthonyshew