https://github.com/quenti-io/quenti

This is the repo running

is that project meant to be run with bun or node?

bun

and railway is running it with only node?

im not entirely sure to be honest. i know railway has the provider listed as node

check the build table

so it seems to be running with bun

does it fail during build or runtime

build

what version of bun are you building it locally with

1.2.0

what version of bun is railway using?

im trying to figure out

bun install v1.1.34 (5e5e7c60) theres this log. i think that is the bun verison

thats a fair bit older given how fast bun does new releases

do you know how I can change the version

nothing comes to mind for a public repo

do they not provide an image?

well i can fork it to run it

not ideal, you may not keep your fork in sync

right. do you know where the version of bun is defined so i can change it at least for personal use? or maybe make a pr

its defined as a nix archive in a nixpacks.toml file

I don't see that in the repo. I'm confused because if its not in the repo, cant it be changed?

it would need to be in the repo to be able to change it

is there instructions somewhere on how to write a nixpacks.toml

looks like you can't even get bun 1.2 on nix

where can i go to see what i can get?

is it a type of provider?

when i search for bun on that search it says its version 1.1.31, but according to railway we're using 1.1.34. Hows that able to happen?

railway is using the unstable archive for bun

gotcha.

so other option is to fork and dockerize

exactly

okay

i plan on turning it into a template

hopefully itll get workin

you will

forked it and removed this text... its working now...

I don't think you should be modifying the authors code like that, there's a reason they set that

its in a config file. i can go and see if i can find the commit it was added in

iit seems to be a bit of a dead project, code hasnt been updated in a year

interesting

do you know how to see the commit a line was changed in perchance? edit: found it

git blame...

apparently its a node deprecation. changing it to with preserves the functionality while not erroring out

did not mean to ping on that sorry