Hey, this is a known issue. On WSL and Remote SSH, cursor-server puts its bundled Node v20.18.2 at the front of PATH, and git hooks via husky pick that up instead of your system nvm or fnm Node. There are similar reports already:
- Old node in cursor (cursor-server)
- ! Cursor Remote SSH regression: cursor-server locked to Node.js 20.18.2, breaking Odoo and all extensions requiring Node.js 22+
- WSL - source control commit using wrong shell
We’re tracking this on our side, but I can’t share an exact fix date yet. As a workaround, you can explicitly call the Node you need in the hook, for example via the absolute path to your nvm version or npx --node-version=22, but that’s a workaround, not a real fix. I’ll post in the thread when we have an update on the fix.