#monorepo yarn + turbo
38 messages · Page 1 of 1 (latest)
Project ID: 62bda654-2934-4aa1-92ce-e7757ed6cdd7
You might find these helpful:
I now have another error: https://srcb.in/DY4I0KidWm
repo?
github repo?
if that, but my repo is private, do I still send the repo link?
bot start-up logs: https://srcb.in/kx6oqCH0HD
do you get these errors on locally?
no, this is the strange thing
do you still get the yarn command not found error
no, but I have another error
now this error appears
tsconfig.json file is in your root folder of the project right
also It looks like some people just updated their ts-node and typescript versions and fixed it
but I don't how your project is structured so I'm not sure if this would solve it
uhhh
can i also see package.json
both that at the root of the project and /apps/bot/package.json
I'm currently thinking this might be because where you run your scripts from
I'm not sure tho
OK, here are both package.json:
bot: https://srcb.in/2vCTNS7qK4
main: https://srcb.in/sQXJqNXcsF
when using typescript, you can give exact location of the typescript config file
maybe you can try that
what do you mean by exact location of the typescript config file?
I was thinking about this
I'm not sure even if it will solve your problem
idk
Is it normal that when I use nixpacks build --config nixpacks.toml --name overwolf/bot .
and it outputs yarn version 1 instead of 3?
here my config nixpacks:
[phases.setup]
nixPkgs = ["nodejs-18_x", "yarn-1_x", "python39", "gccStdenv"]
[phase.name]
aptPkgs = [
"build-essential",
"libcairo2-dev",
"libpango1.0-dev",
"libjpeg-dev",
"libgif-dev",
"librsvg2-dev",
]
[phases.install]
cmds = ["yarn install --check-cache"]
[start]
cmd = "yarn run start"```
You’re specifying yarn v1 in your setup phase, you can change the 1 to a 3 to get yarn v3
Are you sure this version can be included?
actually no, not at all. The latest version is version 1.22.19 according to the npm website
I just assumed it did because you seemed to expect version 3
In that case, what did you mean by this?
I found the problem with tsconfig, it was that root in railway: apps/bot, did not read the original tsconfig