Comment

Comment on The Previous Update Broke Our Bot And I Don't Know Why

Hmm maybe it’s not that simple then. It doesn’t look like the JWT is stored so it’s probably trying to get a new one when started. The other possible culprit would be if you need to use lemmy-js-library with a major version matching the Lemmy server version.

Assuming the server updated to 0.19.0, the version used by the bot is 0.18.0. You would just need to edit package.json so that the lemmy-js-client line reads:

“lemmy-js-client”: “^0.19.0”,

Then running npm install or yarn install (or whatever command you used to install dependencies previously)

source

Sort:hotnew top

MMARefugee@lemmy.world ⁨9⁩ ⁨months⁩ ago
After change:

PS C:\Users***********\Botlt> npm install

npm ERR! code EJSONPARSE

npm ERR! path C:\Users\Josh\Botlt/package.json

npm ERR! JSON.parse Unexpected token ““” (0x201C) in JSON at position 976 while parsing near “… "lemmy-js-client": “^0.19.0”,\r\n "lin…”

npm ERR! JSON.parse Failed to parse JSON data.

npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.

I get the same error just running npm run build as well.

source
- BakedCatboy@lemmy.ml ⁨9⁩ ⁨months⁩ ago
  I think that’s part of the solution, I skimmed some of the forks and found one that updated the lemmy-js-client to 0.19.2-alpha.3 but they made some code changes too to the authentication code. So maybe trying that fork is worth a shot: github.com/thepaperpilot/BotIt
  
  Last changes were last month on that fork
  
  source
  - MMARefugee@lemmy.world ⁨9⁩ ⁨months⁩ ago
    Thanks so much for your help.
    
    I don’t program, and I didn’t even realize there was a fork. Let me root around in there and see what I can find out tomorrow.
    
    Thanks again.
    
    source