node 16 is no longer supported

uh what does that mean and how do i fix this

uh what does that mean

I'm sorry but I'm not sure how I could clarify further.

how do i fix this

set your engines.node to 18 in the package.json

hi sorry for the late reply

thjeres no engines.node in package.json

this is the closest thing i have in package-lock.json

and someone told me to set this to 16 and now ive changed it to 18 but it still doesnt work

1247491307782410290

i think the errors are different thouhg

1247529136268906566

1247531976983052318

add python to the list of providers in your service settings on railway

sorry how exactly do i do that

is it like this?

not quite, please look into your service settings, you will find a providers option, add python with the dropdown

ok i think got it but its still broken

1247691278116716624

oh oops the log got cut off

in the future please use this -

are you using canvas in your project

i dont think so?

if youre talking about this

nope, I'm talking about your code

uhhh i didnt code this im just hosting it so i really dont know

also the bookmarklet doesnt seem to be working for me it just opens a blank page

follow the steps

I'll be brutally honest, it's going to be hard to host a project you don't know anything about, and by extension even harder for me to help you

yea sorry its just that its been working for like 2 years and just randomly stopped

i could asked the person that coded it if you want

you have access to the codebase right? can you send me the package.json please

1247694098383503472

okay thanks, I have an idea that I will put together when I'm back at the computer

ok ty for your help take your time

try adding this as a railway.json file to your project -

{
  "$schema": "https://railway.app/railway.schema.json",
  "build": {
    "builder": "NIXPACKS",
    "nixpacksPlan": {
      "providers": ["node"],
      "phases": {
        "setup": {
          "nixPkgs": ["...", "python3", "gcc"],
          "aptPkgs": ["...", "build-essential", "libcairo2-dev", "libpango1.0-dev", "libjpeg-dev", "libgif-dev", "librsvg2-dev"]
        }
      }
    }
  },
  "deploy": {
    "startCommand": "node index.js "
  }
}

1247698124831588382

that also didnt work

im guessing you really do need node 14, but nixpacks no longer supports node 14

please tell me the timestamp of the last build that did work

4th of april

year?

2024

thanks, where are you obtaining this date from?

i have a log that tracks when the bot goes online and that was the last one

im sorry but thats not what i was asking for

oh

what did you mean then

i would like the timestamp for the last railway build that worked

yea i went back to railway and checked it should be the same

also i did notice the bot started failing while it was still running fine if that helps

okay thank you, just needed to be sure the date was from railway

are you able to share a link to the repo?

https://github.com/MX1D/Guild-Bot-Rewrite

so quick question, where is the railway.json?

oh this is the original one

i added it to mine

whats different about yours?

it should be the same but all the config is filled in and with the railway.json you sent

okay sounds good, ill try some different approaches to get this repo to deploy

i was able to get the repo to deploy.

Remove the railway.json and Procfile, add a Dockerfile with this in it -

FROM node:14-slim

ENV NPM_CONFIG_UPDATE_NOTIFIER=false
ENV NPM_CONFIG_FUND=false

WORKDIR /app

COPY package*.json ./

RUN npm ci

COPY . ./

CMD ["node", "index.js"]

do i just name the file Dockerfile with no extension?

1247707320528535592

correct

please use the bookmarklet

oh right sorry

1247707773253455942

please send your package.json, not the package.json from the repo you sent me

this is the one

thanks, just needed to be sure

copy the package.json and package-lock.json files from this repo into yours

ok now it successsfully deployed but crashed after

what error?

1247713711720759306

interesting, this is proving to be difficult

it used to also spam errors like this in deploy logs but it never affected anything so i just ignored it

in your dockerfile change node:14-slim to node:16-slim

yooo that worked!

tysm for your time

happy to help