Configurator error after update from master

[breadoven]

Updated configurator from current master and no dice trying to get it to run. Returns following error:

 inav-configurator@7.0.0 start /mnt/f/INAVDev/inav-configurator
 node node_modules/gulp/bin/gulp.js build && node node_modules/nw/bin/nw . "."

{ Error: Cannot find module 'node:fs'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/mnt/f/INAVDev/inav-configurator/node_modules/nw-builder/lib/index.cjs:1:24)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3) code: 'MODULE_NOT_FOUND' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! inav-configurator@7.0.0 start: `node node_modules/gulp/bin/gulp.js build && node node_modules/nw/bin/nw . "."`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the inav-configurator@7.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alh/.npm/_logs/2023-11-11T12_58_29_389Z-debug.log

Tried reinstalling npm but still the same error to do with "node:fs".
Any idea how to fix this ?

[breadoven]

OK no idea what's going on with this. It used to run from a Windows Powershell scrip that just runs npm start. However that was failing with the above error after updating from the current master + 7.0.0. Tried running it from Windows Ubuntu WSL using npm start again and the same error. After messing about reinstalling node.js and various other things it now starts using the Powershell script but still throws the above error when trying to run it using Ubuntu even though I'm sure that used to work before. Weird.