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
having the pypi package download both node and the npm package when you first run the pyright command causes some issues:
we have a docker image where all the dependencies are installed, but when the pyright job runs in our CI, it can fail because the runner cannot access npm (due to corporate proxy nonsense). to work around this, we had to put this command in our dockerfile:
npm is incredibly slow and unreliable on PCs at my work
i think bundling the npm package and node in the pypi package would be a much more reliable solution. that's how the playwright pypi package works for example
The text was updated successfully, but these errors were encountered:
[...] It also could skip npm, but I can understand wanting to leverage npm to do version resolution (though doing it just with the registry is not super hard and IMO would be worth it to avoid the dep).
having the pypi package download both node and the npm package when you first run the
pyright
command causes some issues:i think bundling the npm package and node in the pypi package would be a much more reliable solution. that's how the playwright pypi package works for example
The text was updated successfully, but these errors were encountered: