diegosouzapw/OmniRoute v2.6.1

Release v2.6.1 — fix better-sqlite3 startup crash on npm global installs

on GitHub

🐛 Bug Fixes

• fix(build): Force better-sqlite3 to always be required by its exact package name in the webpack server bundle.

  Next.js 16 compiled the instrumentation hook into a separate chunk and emitted require('better-sqlite3-<hash>') — a hashed module name that doesn't exist in node_modules — even though the package was listed in serverExternalPackages. This caused a 500 Internal Server Error on every request for users who globally installed v2.6.0 via npm install -g omniroute. Added an explicit externals function to the server webpack config so the bundler always emits require('better-sqlite3') (exact name).

  Affected: All users who installed OmniRoute v2.6.0 globally via npm install -g omniroute on Linux/macOS.
  Not affected: Docker installs, local dev builds (npm run dev).

  Closes #394, PR #395

🔧 CI

• Added workflow_dispatch to npm-publish.yml with version sync safeguard for manual triggers
• Added workflow_dispatch to docker-publish.yml, updated GitHub Actions to latest versions

⬆️ Update Instructions

npm install -g omniroute@2.6.1
pm2 restart omniroute  # if using PM2

What's Changed

• fix: add workflow_dispatch to docker-publish, update action versions (#392) by @diegosouzapw in #393
• fix(build): force better-sqlite3 webpack external to prevent hash-based module name in instrumentation hook (#394) by @diegosouzapw in #395

Full Changelog: v2.6.0...v2.6.1