You need to commit and push your pnpm-lock.yaml or bun.lockb to your github repo. Railway defaults to using npm if no lockfile is found, and workspace:* is not understood by npm .

I am getting similar for the last 8 hours, did one commit worked fine no issues. 5 mins later same project added sql file to supabase migrations dir and getting similar error to above.

Tried redeploying the commit that built just as test and that doesn't work now either. Haven't changed any settings literally nothing has changed from building and deploying to simply not building anymore.

My fix was i had to add node as the language provider under Metal builds. A bit odd because I didn't change any settings. But it is working now which is the main thing.

What do you mean "under Metal builds" can u do a screenshot?

I’m using npm, not pnpm or a workspace setup.

The issue seems to come from @uniswap/v3-sdk, which includes a broken dependency reference:

@uniswap/sdk-core: workspace:*

This workspace:* syntax is only valid in monorepos using tools like pnpm or yarn workspaces. It is not supported by npm, and since my project is not a workspace, npm cannot resolve it and the install fails.

So the problem is that a published package is referencing a workspace dependency that doesn’t exist in my project?

hey,

the published @uniswap/v3-sdk has workspace:* literally in its package.json for @uniswap/sdk-core, which npm can't handle, that's a bug on uniswap's end not yours

the fix is to add an overrides field in your package.json to force npm to use a real version of @uniswap/sdk-core instead of trying to resolve workspace:*

go to npmjs.com, look up @uniswap/sdk-core, grab the latest stable version number, then add this to your package.json

"overrides": { "@uniswap/sdk-core": "the version you found" }

then delete your package-lock.json and redeploy,

that's it