fix: fail if no lockfile found

[dbarrosop]

No description provided.

[ajgassner]

@dbarrosop I have a menorepo setup with pnpm workspaces and turborepo. The nhost sub-project is in a subfolder <root>/backend/functions. I just have a single lock file in the project root. Any suggestions without ugly workarounds?

First approach:
I have applied following in the root package.json:

  "devDependencies": {
    ....
    "@pnpm/make-dedicated-lockfile": "0.6.15"
  },
  "scripts": {
    ....
    "lock-create": "cd backend/functions && pnpm make-dedicated-lockfile"
  }

However this works locally but not in nhost cloud.

Second approach:
Symlinking also does not help. It seems nhost cloud is working fine with a monorepo/workspace setup.

Third approach / my current solution wich works locally and in the cloud:

1. Create an empty pnpm-lock.yaml in backend/functions
2. Start local nhost nhost up -> pnpm-lock.yaml gets populated

Note: When I make a dependency change in package.json I also have to nhost up again to get a fresh lockfile for the cloud which uses pnpm install --frozen-lockfile. So in addition the dependencies "serverless-http": "3.0.2", "express": "4.18.1" are required to be in package.json.