Closed konosubakonoakua closed 1 month ago
I believe this is a configuration issue on either your local machine or remote machine, which you seem to solve by installing/placing node
on your path? These docs suggest that Pylance should pick up a bundled node executable from VS Code, but from your logs it appears like that setting may have been changed to instead look on the path (per your workaround).
I would suggest engaging with the pylance folks as it seems to either be some assumptions made by that extension, or perhaps configuration on your end that is no longer using their defaults
Workaround: