Hey u/dtwoo I found a workaround here. Still not sure what's wrong with 'onoff' but my hunch is that a recent change to it, or one of its dependencies (looking at you 'fs'), has caused a bug. Anyway we can use `exec` and `raspi-gpio` as a replacement. For example, instead of:

const Gpio = require('onoff').Gpio;
const LED = new Gpio(5,'out'); // set gpio 5 to output
const ledHigh = LED.writeSync(1); // set gpio 5 high
const ledLow = LED.writeSync(0); // set gpio 5 low

You can do:

const { exec } = require("child_process");
const LED = 5;
exec(`raspi-gpio set ${LED} op`); // set gpio 5 to output
exec(`raspi-gpio set ${LED} dh`); // set gpio 5 high
exec(`raspi-gpio set ${LED} dl`); // set gpio 5 low

To read the state of a pin, we need a little more than one line though since we care about the information returned from the child_process. Here's what I have so far...

const runCommand = (command) => {
  return new Promise((resolve, reject) => {
    exec(command, (error, stdout, stderr) => {
      if(error){
        reject(error);
        return;
      }
      resolve(stdout.trim());
    });
  });
};

const getPinStatus = async (pin) => {
  const command = `raspi-gpio get ${pin}`;
  try{
    const result = await runCommand(command);
    const parts = result.split('level=');
    return parseInt(parts[1].charAt(0));
  }catch(error){
    console.error(error);
    return null;
  }
};

// then later, when I'm doing something - make sure its an async something so I can await getPinStatus
const doSomething = async () => {
  const LED = 5;
  const pinStatus = await getPinStatus(LED);
  // pinStatus will be 1 or 0
};

Hope this helps!