Fix: Vibium Install Fails
Vibium install fails? Fix pip install vibium and npm install vibium errors: wrong runtime version, inactive venv, wrong directory, stale package manager.
If Vibium install fails, the cause is almost always your runtime or your environment — not Vibium itself. The fix is usually one of four things: your Python is older than 3.9 (or Node older than 18), your virtual environment isn't active, you're running the script from the wrong folder, or pip/npm is out of date. Vibium installs with a single command — pip install vibium for Python or npm install vibium for Node — which pulls the client plus a platform-specific Go binary; there's no separate ChromeDriver to install, so driver-version errors aren't the issue. Start by confirming your runtime version, then make sure you're installing and running in the same activated environment. Below are the exact errors people hit and how to clear each one. For a clean walkthrough from scratch, see How to install Vibium.
How do I check my runtime version first?
Most install failures trace back to an unsupported runtime, so check that before anything else. Vibium needs Python 3.9+ or Node.js 18+:
python3 --version # need 3.9 or higher
node --version # need v18 or higherIf your version is too old, install a current build from python.org or the LTS release from nodejs.org, then retry the install. An unsupported version is the single most common reason pip install vibium refuses to proceed.
How do I fix "No module named 'vibium'" in Python?
This error means your script and your install are in different environments. You installed Vibium into one environment but are running Python from another — typically because the virtual environment isn't active. Activate it and reinstall:
python3 -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install --upgrade pip
pip install vibiumConfirm it actually landed in the active environment:
pip show vibiumIf pip show finds it but your script still can't, you're running the script with a different Python than the one that's activated. Run it from the same activated venv.
How do I fix "Cannot find module 'vibium'" in Node?
In Node, this error means you're running the script outside the folder where you installed Vibium, or you never ran npm install there. npm installs into the local node_modules of the current project, so the fix is to install in — and run from — the project directory:
cd my-vibium-bot
npm init -y # if there's no package.json yet
npm install vibiumThen run your script from that same folder. If you installed globally and the import still fails, prefer a local install per project; Vibium's binary is resolved relative to the package.
What if pip or npm itself errors out?
When the package manager fails before Vibium is even fetched, it's usually a stale tool or a blocked network. A few targeted fixes:
| Symptom | Likely cause | Fix |
|---|---|---|
| pip resolver or wheel errors | Outdated pip | pip install --upgrade pip then retry |
| Timeouts / connection reset | Network or proxy blocking PyPI/npm | Retry on another network, or configure your proxy |
| Permission denied (global install) | Installing system-wide | Use a venv (Python) or a local project install (Node) |
| Old Vibium pulled in | Cached metadata | pip install --upgrade vibium / npm install vibium@latest |
Using a virtual environment (Python) or a per-project install (Node) sidesteps most permission and version-conflict failures in one move.
Why does the first run feel like part of the install?
If install succeeded but the first launch() hangs or downloads for a while, that's expected — and it's a separate step from installing the package. On first launch, Vibium's Go binary downloads Chrome for Testing, which can take a moment on a slow connection. This is not an install failure; subsequent launches are fast. If that Chrome download itself errors out, that's a distinct problem with its own fixes in Fix: Vibium Chrome download fails.
Why doesn't a missing ChromeDriver break the install?
Vibium never needs ChromeDriver, so "driver not found" style errors don't apply here. The package ships one self-contained Go binary that manages the browser itself and downloads Chrome for Testing on first run. That's why install troubleshooting is really runtime and environment troubleshooting — there's no driver to mismatch, unlike classic Selenium. For the architecture behind that, see How Vibium works.
Still stuck?
If you've confirmed a supported runtime, an active environment, and an up-to-date package manager and install still fails, capture the full error output and open an issue on the Vibium GitHub repository. Include your OS, python3 --version or node --version, and whether you're in a virtual environment.
Next steps
Frequently asked questions
Why does pip install vibium fail?
The most common cause is an unsupported Python — Vibium needs Python 3.9 or newer. Check with python3 --version. Other causes are an inactive virtual environment, an outdated pip, or a network block on PyPI. Upgrade pip and activate your venv, then retry.
Why does 'No module named vibium' appear after installing?
That error means your script is running in a different environment from the one you installed into. Activate the virtual environment where you ran pip install vibium, confirm with pip show vibium, and run the script from that same activated environment.
Does Vibium need ChromeDriver to install?
No. Vibium ships a single Go binary that manages the browser and downloads Chrome for Testing on first launch, so you never install ChromeDriver. If install fails, the problem is your Python or Node runtime or environment, not a missing driver.
Vibium is created by Jason Huggins. This is an independent tutorial — see the official Vibium site and GitHub repo for canonical docs.
Related guides
Fix: Vibium Screenshot Comes Out Blank
Why your Vibium screenshot comes out blank or white, and how to fix it — wait for content, full_page=True, set a viewport, and verify the PNG bytes.
4 min read→TroubleshootingFix: Vibium Chrome Download Fails
Vibium Chrome download fails on first launch? Fix it with vibium install, by clearing network/proxy and disk-space blocks, plus Linux deps.
4 min read→TroubleshootingFix: Vibium 'Element Not Found' Errors
Fix Vibium 'element not found' errors — correct the selector, switch to semantic find, handle iframes and timing, and target elements the way a user sees them.
4 min read→TroubleshootingFix: Flaky Clicks in Vibium
Fix flaky clicks in Vibium — let actionability auto-wait handle timing, target the right element under overlays, and stop adding brittle sleep() calls.
4 min read→