Replies: 3 comments 2 replies
-
|
+1 to this |
Beta Was this translation helpful? Give feedback.
-
|
Hello @sebpowell. Did you have update on this ? |
Beta Was this translation helpful? Give feedback.
-
|
@eliusxpol sorry no – I ended up switching to NX, and so far haven't had any problems. |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried removing just the I have only: I still don't have this working but I seem to be further along. I can deploy the app but it's blowing up with my run command of |
Beta Was this translation helpful? Give feedback.
-
|
@stephenhmarsh I think I probably did try that, but can't say for certain – but for now, I've switched to NX and haven't had any problems so far. I may revisit this setup for future projects. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I'm trying to deploy an app that is part of a monorepo managed by Turborepo to Heroku (the frontends are on Vercel), and running into some problems – hoping someone might have an idea as to what I'm doing wrong (as I suspect the issue is down to how I've configured Turborepo, rather than Heroku).
My repo structure looks like this:
The buildpacks I am using are as follows (loaded in this order):
1.) https://github.com/heroku/heroku-buildpack-multi-procfile
2.) https://github.com/unfold/heroku-buildpack-pnpm
3.) https://github.com/heroku/heroku-buildpack-nodejs
I've also enabled the following environment variables:
The Procfile looks like this:
My root package.json looks like this:
{ "name": "monorepo", "version": "0.0.0", "private": true, "workspaces": [ "packages/*", "apps/*" ], "engines": { "node": "18.14", "npm": "9.8.1", "yarn": "1.22.19" }, "scripts": { "build": "dotenv -- turbo run build", "build:backend": "turbo run build --filter=server", "heroku-postbuild": "pnpm run build:backend", }, "devDependencies": { "dotenv-cli": "^7.2.1", "turbo": "latest" } }The package.json for the server application looks like this:
{ "name": "server", "version": "0.0.1", "scripts": { "build": "nest build", "start": "node dist/main", "dev": "nest start --watch", "start:debug": "nest start --debug --watch", "start:prod": "node dist/main", }, "dependencies": { "@nestjs/common": "^10.0.0", "@nestjs/core": "^10.0.0", "@nestjs/platform-express": "^10.0.0", "@ts-rest/nest": "^3.26.4", "database": "workspace:*", "reflect-metadata": "^0.1.13", "rxjs": "^7.8.1" }, "devDependencies": { "@nestjs/cli": "^10.0.0", "@nestjs/schematics": "^10.0.0", "@nestjs/testing": "^10.0.0", "@types/express": "^4.17.17", "@types/jest": "^29.5.2", "@types/node": "^20.3.1", "@types/supertest": "^2.0.12", "@typescript-eslint/eslint-plugin": "^5.59.11", "@typescript-eslint/parser": "^5.59.11", "eslint": "^8.42.0", "eslint-config-prettier": "^8.8.0", "eslint-plugin-prettier": "^4.2.1", "jest": "^29.5.0", "prettier": "^2.8.8", "source-map-support": "^0.5.21", "supertest": "^6.3.3", "ts-jest": "^29.1.0", "ts-loader": "^9.4.3", "ts-node": "^10.9.1", "tsconfig-paths": "^4.2.0", "typescript": "^5.1.3" }, }And turbo.json, looks like this:
{ "$schema": "https://turbo.build/schema.json", "globalDependencies": ["**/.env.*local"], "pipeline": { "build": { "dependsOn": ["^build", "^db:generate"], "outputs": [".next/**", "!.next/cache/**", "dist/**"] }, "start": { "dependsOn": ["^build"] }, "db:generate": { "cache": false }, "db:migrate": { "cache": false }, "db:push": { "cache": false }, "lint": {}, "test": {}, "test:watch": { "cache": false }, "dev": { "dependsOn": ["^db:generate"], "cache": false } } }When I push to Heroku, everything seems to work as it should, all the way until the end – this is the full output:
One thing that is strange is it looks like it's building twice (?), and that it looks like it's failing due to missing dependencies in an installed package that isn't being used by this application (it is however being used by the other frontend applications). I tried removing all my other apps from the repo, and reran the process – this time, it errored on a different package, suggesting that the issue isn't with the specific package but with the actual build / deploy process:
If you have any ideas, they would be greatly appreciated – I have tried a bunch of different things, and none the wiser. Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions