I have a NextJS app that I'm looking to get running on armv7-unknown-linux-gnueabihf for remote control of an embedded device, using Yocto to build the linux distribution. I'm currently stuck on next-swc failing to find a native binary for this target, which seems to have been removed in https://github.com/vercel/next.js/commit/fed3ffa865464d2a960d8e2fd7468cdef19cd147

I've tried downgrading to the last release version with this target included, next@13.2.4 and eslint-config-next@13.2.4. which when running npm install results in the following error:

npm ERR! code ENOTFOUND
npm ERR! syscall getaddrinfo
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/@typescript-eslint%2feslint-plugin failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/christian/.npm/_logs/2023-11-21T17_52_03_533Z-debug-0.log

(Note: all other dependencies are able to resolve and download just fine, visibly in node_modules/)

I've also tried forking the https://github.com/vercel/next.js repo and re-adding the old configuration for the armv7-unknown-linux-gnueabihf target back to the current github workflow, but that appears to be stuck on a missing TURBO_TOKEN environment variable.

Any help would be appreciated!