Jon Vivian

EDIT: The workaround a posted seems to result in deleting the folder contents on 'npm i' so don't do this: I renamed from `packages/utils` to `packages/@repo__utils`

Workaround is to add empty imports per the error messages, eg: ``` import type {} from "@uploadthing/shared" import type {} from "next/server" ``` edit: added type annotation per suggestion below

Nice, I mostly raised the bug to document the workaround and see if there were any better solutions.

Except it is what is happening. You can test it with the linked reproduction. If you're not convinced - this code produces the same error: ``` import { getImages }...

To be clear, if I move the instantiation into the server action, rather than at the top level of the file, that would also solve the problem. This is a...

Yours has "use server" at the top level of the file, which causes subtly different behavior. My understanding is that will mean that the instantiation of the utapi is encapsulated...

> Please provide a reproduction. https://github.com/4leite/my-turborepo https://github.com/4leite/my-turborepo/actions/runs/9378148823/job/25820887745

What would have been useful is an error saying "This turbo config is for v1 and is not compatible with v2 of turbo, please update your configuration" or something similar.

> Folks, can you confirm for us that you have `turbo` [installed in the repository](https://turbo.build/repo/docs/getting-started/installation#repository-installation)? > > @4leite, I do see that you've done so on your reproduction, thank you....

> @4leite I made a mistake earlier. The reproduction you've provided can't infer down to a 1.x version since it was never installed, so it makes sense that Turborepo 2.0...