a year ago
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "workspace:": workspace:*45 Replies
a year ago
try using pnpm as a package manager instead (or bun or yarn or whatever, ive never gotten npm to work with workspaces)
a year ago
are you using Dockerfile?
if not can you send me your build logs?
I'm not using a dockerfile... or there is no dockerfile within my monorepo
a year ago
it's using npm <:Thinking:1360710341239242762>
a year ago
perfect, then can you show me the top-most part of your build logs?
a year ago
do you have bun specified as your package manager in your package.json?
{
"name": "river",
"private": true,
"scripts": {
"start": "(cd apps/expo && bun start) & (cd apps/backend && bun start:dev)",
"start:beam": "cd apps/beam && bun start",
"lint": "biome check . --write",
"format": "biome format . --write",
"typecheck": "cd apps/expo && bun typecheck",
"prepare": "husky"
},
"workspaces": ["apps/*", "packages/*"],
"devDependencies": {
"husky": "^9.1.7"
}
}a year ago
yea its weird that it's using npm anyway
a year ago
can you try setting your package manager to bun in package.json? maybe that'll make it use bun
a year ago
did you alter the root directory for your service in your service settings?
a year ago
oh okay yea then that's your problem
a year ago
that's only done on isolated monorepos
a year ago
for shared monorepos you deploy the entire repo but alter the start command to point to start whatever app needs to start within the service so that each service runs a different app in the monorepo
a year ago
an isolated monorepo is a monorepo where each repo is completely isolated from the others, meaning no shared folder or packages or anything, each one runs indepedently
a year ago
a shared monorepo is what you have, might have a shared directory, it shares dependencies and such
a year ago
yea
a year ago
I am not sure
a year ago
it's probably fine though
a year ago
i can imagine
a year ago
all good then? clear to mark as solved?
a year ago
sure what's up?
a year ago
Feel free to open up another thread if you still want to ask your question
a year ago
!s
Status changed to Solved dev • 11 months ago



