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 just found out that if clink was failing to show the correct strings for the prompt ({git}, {lambda} etc...) it was because it detected a package.json file in the folder I was accessing, and since this file didn't specify the version of the package (one freshly created with Yeoman), clink just gave up with a
...gram Files\cmder/vendor/clink-completions/npm_prompt.lua:11: attempt to concatenate local 'package_version' (a nil value)
Adding "version":"1.0" in the package.json file actually solved the issue but it would be cool if clink handled that better!
I don't know if it depends on something cmder does or if I should contact the clink devs directly, sorry if it's not where I should post.
The text was updated successfully, but these errors were encountered:
You can also get rid of the error by opening the file "npm_prompt.lua" and replace line 11 with the following:
local package_string = ''
if package_version ~= nil then
package_string = color.color_text("("..package_name.."@"..package_version..")", color.YELLOW)
else
package_string = color.color_text("("..package_name..")", color.YELLOW)
end
I just found out that if clink was failing to show the correct strings for the prompt (
{git}, {lambda}
etc...) it was because it detected a package.json file in the folder I was accessing, and since this file didn't specify the version of the package (one freshly created with Yeoman), clink just gave up with aAdding "version":"1.0" in the package.json file actually solved the issue but it would be cool if clink handled that better!
I don't know if it depends on something cmder does or if I should contact the clink devs directly, sorry if it's not where I should post.
The text was updated successfully, but these errors were encountered: