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
If your project has a pre-commit hook that calls a Node command, and you use VS Code Git Tools to initiate a commit, Volta appears to be finding the default Node instead of the Node specified in package.json.
A possible cause of this is VS Code is somehow executing the Git commit with a cwd that is outside of the project, causing Volta to start in the wrong directory and not find the project-local settings. If possible, we should correctly handle this case, or worst provide some guidance for how to set up VS Code to get the expected behavior.
The text was updated successfully, but these errors were encountered:
If your project has a pre-commit hook that calls a Node command, and you use VS Code Git Tools to initiate a commit, Volta appears to be finding the default Node instead of the Node specified in
package.json
.A possible cause of this is VS Code is somehow executing the Git commit with a
cwd
that is outside of the project, causing Volta to start in the wrong directory and not find the project-local settings. If possible, we should correctly handle this case, or worst provide some guidance for how to set up VS Code to get the expected behavior.The text was updated successfully, but these errors were encountered: