Replies: 3 comments
-
Hi @kasper573, I got the same issue, any solutions or workaround so far? |
Beta Was this translation helpful? Give feedback.
0 replies
-
@kennaruk Yeah I worked around it by bundling the server code and pointing the vercel api entrypoint to the bundle instead. It works all right. You can see how I did here |
Beta Was this translation helpful? Give feedback.
0 replies
-
Workaround for me was using a bundler like tsdown in combination with vercel primitives and prebuilt deployment. Solution was inspired by: I wrote more in-depth about the approach for my project here: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I just ran into an error after adding an internal package (https://turbo.build/repo/docs/handbook/sharing-code/internal-packages) to my api app in my turborepo. The api plugs into Vercels serverless functions using a standalone express app (https://vercel.com/guides/using-express-with-vercel#standalone-express), and it worked just fine before adding a workspace:* dependency.
As soon as I added the new dependency I'm getting this runtime error:
Cannot find module '/var/task/apps/graphql-api/node_modules/favorite-movies-db-client/src/index.ts' Did you forget to add it to "dependencies" in package.json? RequestId: 9161c7b9-5bf3-4eee-b943-42c63ab447a9 Error: Runtime exited with error: exit status 1 Runtime.ExitError
Is this supposed to be working or am I trying to do something that's not supported?
Beta Was this translation helpful? Give feedback.
All reactions