UbuCon India 2026 · Workshop

Scaling Local AI: Benchmarking vLLM and Building Personal Agents

Pre-setup: get nvm + Node.js 22.23.2 running on your laptop before the session.

  • PresenterSayed Imran
  • WhenSun, 15 Nov 2026 · 15:35–16:35 IST
  • TrackArtificial Intelligence & Machine Learning (AI/ML)
  • VenueWorkshop Room, Bengaluru
View session on the UbuCon India schedule

Please finish this before the workshop. It takes about 10–15 minutes. Everyone needs the exact same Node version so the packages behave the same for all of us.

Node.js 22.23.2 npm 10.x (comes with Node) Installed via nvm Best on Ubuntu 22.04 / 24.04 LTS
Windows 10 is not supported for this workshop Some workshop packages compile native code during npm install, and this has failed on Windows 10 before. On Windows, please use Windows 11 (64-bit). If your laptop runs Windows 10, upgrade to Windows 11, run Ubuntu instead (dual boot or a virtual machine), or contact the organiser before the workshop.

Requirements at a glance

OSMinimumTool
Ubuntu (recommended)Ubuntu 22.04 or 24.04 LTS, 64-bit (other distros with glibc 2.28+ also work)nvm
WindowsWindows 11, 64-bit only (Windows 10 is not supported)nvm-windows
macOSmacOS 11 Big Sur or newer (Intel or Apple Silicon)nvm

Install for your operating system

  1. Check your Ubuntu version

    lsb_release -ds; uname -m

    You want Ubuntu 22.04 or 24.04 LTS on x86_64 or aarch64. Older releases may work but aren't tested for the workshop.

  2. Remove apt / snap Node (if any)

    Node from apt or snap will clash with nvm. Check with which -a node, then remove it:

    sudo apt remove -y nodejs npm 2>/dev/null; sudo snap remove node 2>/dev/null; hash -r
  3. Install curl and build tools

    Ubuntu / Debian / Ubuntu on WSL
    sudo apt update && sudo apt install -y curl build-essential python3
    Fedora / RHEL
    sudo dnf install -y curl gcc-c++ make python3
  4. Install nvm

    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash

    Reload your shell (or open a new terminal):

    source ~/.bashrc
  5. Install and use Node 22.23.2

    nvm install 22.23.2
    nvm use 22.23.2
    nvm alias default 22.23.2
Don't use sudo with npm With nvm, global installs go into your home folder. If npm install -g asks for sudo, nvm isn't active — open a new terminal and run nvm use 22.23.2.

Verify your setup

Open a new terminal and run:

node -v
npm -v
node -p "process.platform + ' ' + process.arch"

Expected output:

v22.23.2
10.x.x
win32 x64      (or darwin arm64 / darwin x64 / linux x64)

Native module smoke test

This confirms native packages can be installed on your machine (the issue we hit last time). Run it in an empty folder:

mkdir node-check && cd node-check
npm init -y
npm install bcrypt --build-from-source
node -e "require('bcrypt'); console.log('Native modules OK')"

If you see Native modules OK, you're ready. You can delete the node-check folder afterwards.

Pre-workshop checklist

Troubleshooting

nvm is not recognised / command not found

Close all terminal windows and open a new one. On Windows, sign out and back in if it still fails. On macOS/Linux, check that ~/.zshrc or ~/.bashrc contains the NVM_DIR lines added by the installer.

node -v shows a different version

Another Node installation is earlier on your PATH. Run where node (Windows) or which -a node (macOS/Linux) and uninstall anything not managed by nvm. Then run nvm use 22.23.2 again.

Windows: nvm use says "exit status 1" or "Access is denied"

Run the terminal as Administrator. Also make sure your Windows username / nvm install path has no special characters; if it does, reinstall nvm-windows to C:\nvm and set the Node symlink to C:\nodejs during setup.

Windows: gyp ERR!, MSBuild or "Could not find any Visual Studio installation"

The C++ build tools are missing or incomplete. Redo Step 3 in the Windows tab, restart the PC, then retry. If it still fails, switch to the Ubuntu on WSL2 option.

Windows: errors mentioning ENAMETOOLONG or paths that are too long

Enable long paths (Step 4 in the Windows tab), restart, and keep projects in a short path like C:\dev\workshop.

Corporate laptop / proxy blocks downloads

Ask your IT team to allow nodejs.org, registry.npmjs.org and github.com, or use a personal laptop for the workshop.

Why exactly 22.23.2? The workshop project and its dependencies were tested on this version. We pin it on purpose and use nvm so it doesn't affect any other Node version you use for your own projects. Switch back any time with nvm use <version>.