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
Is your feature request related to a problem? Please describe.
I installed the CLI globally using bun. I did not get an error during installation.
When I ran the app, I got an error TypeError: shellPath.at is not a function.
I noticed that I was running node 14 in my path, which is not supported.
Describe the solution you'd like
I suggest checking node's version at startup and fail with an error if the version is not supported.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
tram98
changed the title
Stop oclif-CLI with an error when node version is not satisfied
Stop oclif-CLI with an error when node version is not supported
Sep 20, 2024
We had a check for this at one point in time but removed it because we thought it was unnecessary since npm install will fail when the engine property isn't satisfied.
I'm not super familiar with bun but it seems that bun install doesn't check the node engine property on install
Is your feature request related to a problem? Please describe.
I installed the CLI globally using bun. I did not get an error during installation.
When I ran the app, I got an error
TypeError: shellPath.at is not a function
.I noticed that I was running node 14 in my path, which is not supported.
Describe the solution you'd like
I suggest checking node's version at startup and fail with an error if the version is not supported.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: