The output there shows it trying to do | Foundry VTT | Page 1

crimson ivy Jun 15, 2024, 2:03 PM

#

I did the Pixi reinstall yesterday. This is the error that I get now when running this:

npm ERR! code EJSONPARSE
npm ERR! path /home/pi/foundryvtt/resources/app/package.json
npm ERR! JSON.parse Unexpected end of JSON input while parsing empty string
npm ERR! JSON.parse Failed to parse JSON data.
npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.

npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-06-15T14_01_19_108Z-debug-0.log```

glacial cypress Jun 15, 2024, 2:04 PM

#

crimson ivy I did the Pixi reinstall yesterday. This is the error that I get now when runnin...

What do you mean by "Pixi reinstall"?

crimson ivy Jun 15, 2024, 2:04 PM

#

I uninstalled Pixi.js
I installed Pixi.js

glacial cypress Jun 15, 2024, 2:04 PM

#

crimson ivy I uninstalled Pixi.js I installed Pixi.js

Uhh... why would you do that?

#

And what exactly did you do?

#

You shouldn't ever have to do that, so I have no idea what the state of your install is now

blazing canopy Jun 15, 2024, 2:06 PM

#

You should probably delete that entire install and start fresh at this point

crimson ivy Jun 15, 2024, 2:07 PM

#

glacial cypress And what exactly did you do?

https://github.com/pixijs/pixijs/wiki/Upgrading-PixiJS

GitHub

Upgrading PixiJS

The HTML5 Creation Engine: Create beautiful digital content with the fastest, most flexible 2D WebGL renderer. - pixijs/pixijs

#

The errors I posted were referring to issues with PixiJS. I can uninstall it if that is what is needed. I reverted back to V11 fine with the current settings.

glacial cypress Jun 15, 2024, 2:08 PM

#

crimson ivy https://github.com/pixijs/pixijs/wiki/Upgrading-PixiJS

Foundry ships with a very specific version of Pixi, and you never need to upgrade or uninstall/reinstall it on its own.

#

You'll need to delete this Foundry install folder and start over, as you've put it into some kind of inconsistent state

crimson ivy Jun 15, 2024, 2:08 PM

#

glacial cypress Foundry ships with a very specific version of Pixi, and you never need to upgrad...

I can see that from what you are repeating, but the errors I read indicated that it was necessary

#

I was explaining why I took the action.

glacial cypress Jun 15, 2024, 2:09 PM

#

I understand that, and what I'm saying is that the errors must have been a red herring or caused by something else.

#

If you upgrade Pixi, you'll break your Foundry install.

#

So you'll need to delete that folder, and restart so we're not starting from a broken installation

crimson ivy Jun 15, 2024, 2:11 PM

#

I have removed them. What would you advise next?

blazing canopy Jun 15, 2024, 2:11 PM

#

Did you extra a fresh install already?

crimson ivy Jun 15, 2024, 2:12 PM

#

I did not. The Pixi version on the pi is still the same, so I want to make sure I am following directions here.

blazing canopy Jun 15, 2024, 2:12 PM

#

pixijs isn't a global install. It's specific to the foundry install

glacial cypress Jun 15, 2024, 2:12 PM

#

To be clear, when you said you "removed them" do you mean you did an rm -r on the Foundry installation folder?

crimson ivy Jun 15, 2024, 2:13 PM

#

rm -rf some_dir

glacial cypress Jun 15, 2024, 2:14 PM

#

Then let's re-extract Foundry using this

wget --output-document ~/foundry/foundryvtt.zip "<download url>"```

#

rm ~/foundry/foundryvtt.zip```

#

Or whatever folder structure you have

crimson ivy Jun 15, 2024, 2:15 PM

#

All set

glacial cypress Jun 15, 2024, 2:16 PM

#

Alright... and before we continue, let's just make sure. What's the output of node --version?

crimson ivy Jun 15, 2024, 2:16 PM

#

pi@raspberrypi:~ $ node --version
v18.16.0

blazing canopy Jun 15, 2024, 2:18 PM

#

Are you trying to run v12 along side your v11 install?

crimson ivy Jun 15, 2024, 2:19 PM

#

No. I am upgrading to V12.

blazing canopy Jun 15, 2024, 2:20 PM

#

Okay lets see if you still get the glib error when you launch Foundry
node ~/foundry/resources/app/main.js

crimson ivy Jun 15, 2024, 2:20 PM

#

node:internal/modules/cjs/loader:1078
  throw err;
  ^

Error: Cannot find module '/home/pi/foundry/resources/app/main.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
    at Module._load (node:internal/modules/cjs/loader:920:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.16.0```

blazing canopy Jun 15, 2024, 2:21 PM

#

did you change the path that threz gave you at all?

crimson ivy Jun 15, 2024, 2:22 PM

#

Yes.
foundryvtt is the folder that it uses. Let re-run it.

#

node:internal/modules/cjs/loader:1338
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /home/pi/foundryvtt/resources/app/node_modules/classic-level/prebuilds/linux-arm/node.napi.armv7.node)
    at Module._extensions..node (node:internal/modules/cjs/loader:1338:18)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at load (/home/pi/foundryvtt/resources/app/node_modules/node-gyp-build/node-gyp-build.js:22:10)
    at Object.<anonymous> (/home/pi/foundryvtt/resources/app/node_modules/classic-level/binding.js:1:43)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/home/pi/foundryvtt/resources/app/node_modules/classic-level/index.js:7:17)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.16.0```

blazing canopy Jun 15, 2024, 2:23 PM

#

Okay run cd ~/foundryvtt/resources/app/

crimson ivy Jun 15, 2024, 2:23 PM

#

in it

blazing canopy Jun 15, 2024, 2:23 PM

#

Then run npm install classic-level --build-from-source

crimson ivy Jun 15, 2024, 2:25 PM

#


added 7 packages, changed 19 packages, and audited 546 packages in 1m

55 packages are looking for funding
  run `npm fund` for details

10 vulnerabilities (4 moderate, 3 high, 3 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues possible (including breaking changes), run:
  npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.```

blazing canopy Jun 15, 2024, 2:25 PM

#

now node ~/foundryvtt/resources/app/main.js

crimson ivy Jun 15, 2024, 2:26 PM

#

It looks to be running. Thank you.

#The output there shows it trying to do