I'm running through the slice machine tutorial.
I've encountered an error while trying to
Push Slice to Prismic. The browser simply hangs on this step. Storybook is running and shows the slice as expected.
Console logs are as follows:
> email@example.com slicemachine > start-slicemachine --port 9999 [slice-machine] Launching server [slice-machine] Now running on http://localhost:9999 ! [slice-machine] (node:11888) UnhandledPromiseRejectionWarning: Error: Failed to launch the browser process! /home/cnielsen/projects/prismic/slice-library-starter-next/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/cnielsen/projects/prismic/slice-library-starter-next/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20) at Interface.<anonymous> (/home/cnielsen/projects/prismic/slice-library-starter-next/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68) at Interface.emit (events.js:327:22) at Interface.EventEmitter.emit (domain.js:467:12) at Interface.close (readline.js:424:8) at Socket.onend (readline.js:202:10) at Socket.emit (events.js:327:22) at Socket.EventEmitter.emit (domain.js:467:12) at endReadableNT (internal/streams/readable.js:1327:12) at processTicksAndRejections (internal/process/task_queues.js:80:21) (Use `node --trace-warnings ...` to show where the warning was created) [slice-machine] (node:11888) 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:11888) [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.
I searched the forums and found this post, which I think is related: Slice Machine in Next.js example, using WSL2 (Windows). However, that poster solved the problem by adding
@storybook/react to their
devDependencies. I don't think that will help me because I already have
@storybook/react in my
What should my next steps be?