gbockus-sf

Howdy, I tried to repo this on Mac and Windows without success. I just updated the extensions this morning and refreshed VSCode. This kind of error typically indicates there is...

Hum. Very strange. I had @randi274 also try it on her windows box and she was also unable to reproduce. Could you please share the output from `ls ~/.vscode/extensions` Also...

@Sainath-Attuluri @ronika-das My apologies on it taking so long to get back to this issue. I've assigned it to myself so it doesn't slip off the radar again. Everything looks...

HI @pledbetter-cvet Can you provide a specific case where it's taking a long time to deploy? Attempt a single file deploy and keep track of the amount of time it...

vsixes should be included in releases now. We had an issue with our release process but it has been resolved.

@AngelMtz97 Sorry for the long delay. I've assigned this issue to myself so we can get it to resolution. As a test if you clone a sample repo (like [ebikes](https://github.com/trailheadapps/ebikes-lwc))...

No worries. I'll just close this issue for now and if it ever reappears just let us know. I suspect it was either something about how the cli was configured...

We've been moving to using shared libraries instead of utilizing the cli directly in the vscode extensions for a while as there is a performance cost to starting the cli...

@perryton my apologies on the slow response. This is not something we were tracking on the vscode side. I'll mark this as a bug so it's raised up internally as...

Hey Ed. Thanks for reporting. We're currently defaulting to node 16.13 locally for development ( and npm 8 but you're already there). We're chopping away at those outdated dependancies but...