SyntaxError: Unexpected reserved word at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)

[ryancwalsh]

SyntaxError: Unexpected reserved word at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)

[ryancwalsh]

I think I had Node.js: v18.18.0 via nvm but 12.12 on my system. So I uninstalled node at my system level so that now Node only exists via nvm.

Now I get this error in my commit attempt:

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
/usr/bin/env: ‘node’: No such file or directory
husky - pre-commit hook exited with code 127 (error)

[ryancwalsh]

As I mentioned at https://stackoverflow.com/questions/67063993/sh-husky-command-not-found#comment136565022_72617424, I'll now try to figure out whether VSC is the problem.

Husky successfully called lint-staged when I do the git commit in the Ubuntu terminal instead of VSC, even without making a ~/.huskyrc as https://typicode.github.io/husky/troubleshooting.html suggests.

I thought typicode/husky#953 or ohmyzsh/ohmyzsh#9252 or typicode/husky#1025 or https://stackoverflow.com/questions/67198286/how-to-make-shell-agnostic-a-husky-hook would be related, but now I think there is just something about VSC that I need to learn.

[iiroj]

Unfortunately I can't give support for configuration setup on Ubuntu, but it sounds like you are on the right track. If lint-staged works in your terminal but not when called through husky, I would take a look at where node is installed and whether it's available in your $PATH.

[ryancwalsh]

Thanks.