ChrisEric1.GitHub.io icon indicating copy to clipboard operation
ChrisEric1.GitHub.io copied to clipboard

Lightcord does not load

Open moxie-coder opened this issue 9 months ago • 5 comments

I get these two errors when trying to use it, it seems like I'm not doing this correctly or something, but it's not working (in fact I don't even know which one to install because there's many, but I do know not to use the ARM version since I use x86-64 windows, not ARM, and my pc is 64 bit btw)

Image

Image

moxie-coder avatar Feb 26 '25 22:02 moxie-coder

I think the Lightcord release got corrupted somehow when I uploaded it however long-ago now, because when I was doing this issue, I had to git clone http://github.com/ChrisEric1/ChrisEric1.GitHub.io && cd ChrisEric1.GitHub.io && cd Lightcord && npm run devInstall && npm run run just so I can get in. I'll see if I can re-build it later today (its 2AM when I am wrtiing this reply right now)

Update (as of 2:30AM): LBC-windows-dir-x64.zip doesn't seem to work, as per this issue, but LBC-windows-dir-ia32.zip does, which will, however, use WoW64 if on x64 Windows

Note the syntax, (D/L)BC-(windows/macos/linux)-dir-(armv7/arm64/ia32/x64).zip, you usually want the dir release because the other compression releases have the dir in them, making them a slight bit too big of a download (I didn't know this myself until the release was already published)

CE1CECL avatar Feb 27 '25 07:02 CE1CECL

alright, good to know the 64 bit releases got corrupted somehow, I can use 32 bit apps fine, it hasn’t gotten over 4GB of RAM in the DBC client

moxie-coder avatar Feb 27 '25 12:02 moxie-coder

okay so the 32 bit build seems to give me an 403 forbidden error on startup, and never starts up after that, and trying to compile just gives me this

error!
{
  error: Error: spawnSync npm.cmd EINVAL
      at Object.spawnSync (node:internal/child_process:1120:20)
      at Object.spawnSync (node:child_process:868:24)
      at spawnProcess (C:\Users\freem\ChrisEric1.GitHub.io\Lightcord\scripts\devInstall.js:9:32)
      at Object.<anonymous> (C:\Users\freem\ChrisEric1.GitHub.io\Lightcord\scripts\devInstall.js:22:1)
      at Module._compile (node:internal/modules/cjs/loader:1565:14)
      at Object..js (node:internal/modules/cjs/loader:1708:10)
      at Module.load (node:internal/modules/cjs/loader:1318:32)
      at Function._load (node:internal/modules/cjs/loader:1128:12)
      at TracingChannel.traceSync (node:diagnostics_channel:322:14)
      at wrapModuleLoad (node:internal/modules/cjs/loader:219:24) {
    errno: -4071,
    code: 'EINVAL',
    syscall: 'spawnSync npm.cmd',
    path: 'npm.cmd',
    spawnargs: [ 'rm', 'electron' ]
  },
  status: null,
  signal: null,
  output: null,
  pid: 0,
  stdout: undefined,
  stderr: undefined
}
undefined

so looks like this issue isn't exactly solved yet

moxie-coder avatar Mar 16 '25 16:03 moxie-coder

What Node.JS version are you using? IIRC you need v12 to prevent any Lightcord build issues.

CE1CECL avatar Mar 17 '25 19:03 CE1CECL

What Node.JS version are you using? IIRC you need v12 to prevent any Lightcord build issues.

v22.12.0 that's good to know

moxie-coder avatar Mar 17 '25 19:03 moxie-coder