Unable to launch app with Chromebook

[isabellittle]

I'm experimenting with a new setup while the site is down. I was able to successfully run the app on my MacBook, but having a lot more trouble with a Chromebook.

Finally installed nodejs in the Linux environment after a lot of trial and error, but now I can't get the app to start after installing all dependencies. See full error message below.

Any insight? Is there some fundamental incompatibility with using a Chromebook?

`isabellittle16@penguin:~/miq-nz-booking-tools-0.10.4/MIQ-Booking-Assistance$ npm start

[email protected] start /home/isabellittle16/miq-nz-booking-tools-0.10.4/MIQ-Booking-Assistance
npx run-func miq-assistance.js start

npx: installed 1 in 4.353s
(node:5056) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process!
/home/isabellittle16/miq-nz-booking-tools-0.10.4/MIQ-Booking-Assistance/node_modules/puppeteer/.local-chromium/linux-818858/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

at onClose (/home/isabellittle16/miq-nz-booking-tools-0.10.4/MIQ-Booking-Assistance/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
at Interface.<anonymous> (/home/isabellittle16/miq-nz-booking-tools-0.10.4/MIQ-Booking-Assistance/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
at Interface.emit (events.js:412:35)
at Interface.close (readline.js:451:8)
at Socket.onend (readline.js:224:10)
at Socket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1317:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)

(Use node --trace-warnings ... to show where the warning was created)
(node:5056) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:5056) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.`