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
Executing npm modules as separate processes on Windows requires including their file extensions. For example, "eslint" should be "eslint.cmd".
The solution would look like this:
function lint.command(cmd)
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
if PLATFORM == "Windows" then
table.insert(cmd, 1, "/C")
table.insert(cmd, 1, "cmd.exe")
end
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
return function (filename)
return map(cmd, function (k, v)
if type(k) == "number" and v == lint.filename then
return filename
end
return v
end)
end
end
However, I believe encapsulating all Windows commands after "cmd.exe /C" without offering an option within the linter script to bypass this encapsulation isn't the most effective approach. Additionally, there's currently no way to send something like 'windows_skip_cmd' flag to customize the command's construction, without breaking changes.
The text was updated successfully, but these errors were encountered:
andreivinca
changed the title
npm and other command from Windows
npm and other commands from Windows
Feb 13, 2024
Executing npm modules as separate processes on Windows requires including their file extensions. For example, "eslint" should be "eslint.cmd".
The solution would look like this:
However, I believe encapsulating all Windows commands after "cmd.exe /C" without offering an option within the linter script to bypass this encapsulation isn't the most effective approach. Additionally, there's currently no way to send something like 'windows_skip_cmd' flag to customize the command's construction, without breaking changes.
The text was updated successfully, but these errors were encountered: