[Bug]: Wrong Architecture

[whizkidTRW]

What happened?

On windows 11, I cloned the repo and when I did the 'npm install' it errored out with unsupported platform for [email protected].

Version

3.0.4

Distribution

Source

OS

Windows

What browsers are you seeing the problem on?

No response

If applicable, What Listener Clients are You Using?

No response

TallyArbiter configuration

N/A - no config yet, won't install!

Relevant log output

C:\tallyarbiter>npm install
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   win32
npm ERR! notsup Actual Arch: x64

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Todd\AppData\Roaming\npm-cache\_logs\2023-11-13T21_20_19_033Z-debug.log

Error stacktrace (if applicable)

No response

[github-actions]

Hello there whizkidTRW 👋

Welcome to TallyArbiter!

Thank you for opening your first issue for the Tally Arbiter project. Tally Arbiter fosters an open and welcoming environment for all our contributors. Please adhere to our Code Of Conduct.

If you have more to contribute to this issue, please comment down below! We will try to get back to you as soon as we can.

[hrueger]

This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!

make sure to use a more recent version of npm. If that does not fix the issue, most of the dependencies of this project could probably be updated ;-) Unfortunately, due to university I don't have time to work on this currently and in the near future.

[whizkidTRW]

No worries! I noticed that I was running nodeJS v14 after I posted this. I didn't realize it was so horribly out of date! After upgrading to v20, it's working much better now, though I'm still not getting tally from my ATEM Mini, but I'm still working on it. Thanks! Todd Witten ***@***.***

…

On Mon, Nov 13, 2023 at 3:40 PM Hannes Rüger ***@***.***> wrote: This version of npm is compatible with ***@***.***, but package-lock.json was generated for ***@***.*** I'll try to do my best with it! make sure to use a more recent version of npm. If that does not fix the issue, most of the dependencies of this project could probably be updated ;-) Unfortunately, due to university I don't have time to work on this currently and in the near future. — Reply to this email directly, view it on GitHub <#608 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHWZ2KS5XFG25G5R3Q3WYG3YEKHTPAVCNFSM6AAAAAA7JZSHI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZGE3TCMRUGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[hrueger]

Can we close this then?

[whizkidTRW]

Yes, absolutely. Thanks! Todd Witten ***@***.***

…

On Tue, Nov 14, 2023 at 3:50 AM Hannes Rüger ***@***.***> wrote: Can we close this then? — Reply to this email directly, view it on GitHub <#608 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHWZ2KR35DVIHMZQ2JI2253YEM5FDAVCNFSM6AAAAAA7JZSHI6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBZHA3TMMJVGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>