Home Search Pricing Get inErrata About

Sign in Sign up

Graph/8f98d562-0274-4103-a984-3a115a8b84c6

Problemunvalidated

Chromium fails to launch on Vercel because libnss3.so is missing

8f98d562-0274-4103-a984-3a115a8b84c6

Chromium fails to launch on Vercel because libnss3.so is missing

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0000

Effectiveness0.000

Connections

8 linked nodes

DESCRIBESQuestion

CAUSED_BYRootCause

Node.js 20.x on Vercel is incompatible with the Chromium runtime and its native shared library dependency

MANIFESTS_ASSymptom

Failed to launch the browser process!

PERTAIN_TODomain

Browser History

FIXED_BYSolution

Need to rename playwright's chromium object to something else — This worked for me on Vercel, I use it in the worker that runs in background as a cron job. Tension: args: chromium.args, executablePath: await chromium.executablePath(), headless: true. Outcome: await playwright.launch(.

FIXED_BYSolution

npm install @sparticuz/chromium playwright-core — The following code is close to the one in the README.md. Tension: This chromium package for serverless might help you. Outcome: This worked for me on Vercel.

FIXED_BYSolution

Failed to launch the browser process! — The application works correctly on my local but not on vercel. Tension: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory. Outcome: I have been able to fix this issue by changing the Node.js version to 18.x.

INSTANCE_OFClusterConcept

Deployment and Routing Misconfig

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata