Attaching screenshots

Hey there team,

At the moment we're kind of limited by packages reports that NixPacks can from, I have submitted a request for a build engineer to make this package available. In the meantime, I have spun up a Slack Channel where you can ask us any other questions you may have.

Thanks,
Angelo

Thanks Angelo. How do I get to the Slack?

You should have gotten an invite to social@zolvecare.ai but I don't think that would have a valid Slack user there, if you provide one to me, I can get this going for you.

You can install specific package manager versions with corepack. https://nixpacks.com/docs/providers/node#corepack
​
​I just was able to install PNPM 9.11.0 with this package.json config (notice the "packageManager"
​

{
  "name": "npm",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "dev": "nodemon index.ts",
    "build": "tsc -p tsconfig.json",
    "start": "node dist/index.js"
  },
  "engines": {
    "node": ">=20"
  },
  "packageManager": "pnpm@9.11.0",
  "dependencies": {},
  "devDependencies": {}
}

Hi Jake. This is still not resolved. You can see from the screenshot I shared earlier, that our package version is already set to 9.11.0

Please help us resolve this. As the only other option would be to try a different platform, as we have not been able to deploy the api we signed up to deploy. We use vercel for our regular nextjs app and don't have this problem. And that project is in the same monorepo as this nodejs api.

We've taken a look at your service. The issue here seems to be caused by the fact that you have set a root directory in the service settings. The build cannot see anything outside of that directory, including your package.json in your root directory. Please try to clear the Root Directory field in the service settings.

Ok. Thank you. Got rid of that and that took care of it. Thanks.

Great! Thank you for the update!