Hey @leegee! Vercel has some documentation on using monorepos. It usually helps people get their monorepo projects deployed. Can you give that a try and let me know if it works for you?

https://vercel.com/docs/monorepos#using-monorepos

vercel.com

Using Monorepos

Vercel provides support for monorepos. Learn how to deploy a monorepo here.

Thank you very much for the link to the docs, which gives me the understand that I need to have a separate project for each package in the monorepo that I wish to deploy, which makes perfect sense.

My root package.json has a devDependency on rimraf, and the Vercel build says sh: line 1: rimraf: command not found, despite rimraf being listed in the package.json devDependencies.

rimraf is not listed in the package.json of the monorepo package being installed, because that would seem to be best practice, but perhaps it is a requirement of Vercel...?

Thanks in anticipation of any pointers, Lee

Thanks for your patience. Did you find a solution?

If not, a minimal reproducible example would help me see what you see so I can help you debug.

I am making progress, thanks.

Currently I am trying to find a way to have my npm monorepo share dependencies from node_modules on Vercel as it does locally.

That is, the root package.json declares dependencies and they are housed in node_modules/, but it seems the way I am (mis-) configuring vercel.json means that I would have to redeclare dependencies in every package.json, which makes me think I am doing something wrong!

1
{
2
  "version": 2,
3

4
  "build": {
5
    "env": {
6
      "NODE_ENV": "production",
7
      "VITE_HTTP_PORT": "3000",
8
      "VITE_ENDPOINT_SEARCH": "/api/search",
9
      "VITE_ENDPOINT_DETAILS": "/api/details",
10
      "DATABASE_URL": "postgres://testac:testpassword@localhost:5432/ufo"
11
    }
12
  },
13

14
  "builds": [
15
    {
16
      "src": "packages/client/dist/**/*",
17
      "use": "@vercel/static"
18
    },
19

20
    {
21
      "src": "packages/vercel/build/**/*",
22
      "use": "@vercel/node"
23
    }
24
  ],
25
  "routes": [
26
    {
27
      "src": "/api/search",
28
      "dest": "packages/vercel/build/search.js"
29
    },
30

31
    {
32
      "src": "/api/hello",
33
      "dest": "packages/vercel/build/hello.js"
34
    },
35

36
    {
37
      "src": "/(.*)",
38
      "dest": "packages/client/dist/$1"
39
    }
40
  ]
41
}

That is, I've followed the instructions in the link kindly provided above, but although I see that dependencies are installed by the root package.json, they are not found the sub-package when it builds in packages/client.

@leegee

Did you try setting a base directory and running npm run build (for example) you might try leaving the base directory empty and setting the build command to (for example)

1
cd path/to/app && npm run build

and setting the publish directory to path/to/app/BUILD there BUILD is the name of the output directory (e.g build, or dist.)

The best way would still be to create multiple package.json in the entire repo. Then when you actually start the build, either:

1. cp ../package.json ./package.json && npm i && npm run build OR
2. cd ../ && npm i && cd ./sub-folder/ && npm run build

Basically, you will have to change your command to manually install your packages. So you can either do that by copying your package.json to your cwd or cd into the parent directory, install packages, cd back into your project directory and run the build.

Give it a try and let me know if it helps.

Thanks for your reply.

My conclusion is that I do not think Vercel supports npm monorepos, so I'm looking at using Turborepo now, though the Vercel docs are not clear on its use, that is another ticket..!

Thanks again, both.