You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was asked by a downstream project to share this issue with you.
The issue involves an error where npm is trying to access the incorrect path (ib/ instead of lib/) when non-LTS versions of Node.js (like v23.0.0+) are installed via nodeenv. This causes an ENOENT error, and the problem arises specifically with versions of Node.js that are not LTS. The suggestion is to default to LTS or allow a configuration option for specifying the Node.js version in nodeenv.
Hey 👋🏻
I was asked by a downstream project to share this issue with you.
The issue involves an error where npm is trying to access the incorrect path (
ib/
instead oflib/
) when non-LTS versions of Node.js (like v23.0.0+) are installed via nodeenv. This causes an ENOENT error, and the problem arises specifically with versions of Node.js that are not LTS. The suggestion is to default to LTS or allow a configuration option for specifying the Node.js version in nodeenv.See this issue for more details -> pre-commit/pre-commit#3339
The text was updated successfully, but these errors were encountered: