Doug Bunting

> Where are we supposed to run this? In the same directory as that .npmrc and the changed package.json file.

The system automatically loads packages from upstream repositories into the one listed in the .npmrc file when an authorized person runs `yarn install`. That means only authorized people (like you)...

No, execute it from the command line using the .npmrc file I mentioned. Then, you're authenticated and `yarn install` should do the right thing, assuming your cache is clear and...

@captainsafia @javiercn where exactly is this PR❔ Do one of you already have updated lock files on your machines❔

@dotnet/aspnet-blazor-eng I updated the lock files and we're getting further. But it appears the newer packages include a breaking change: ``` text > selenium-standalone start --config /home/vsts/work/1/s/src/Shared/E2ETesting/selenium-config.json --javaArgs=-Dwebdriver.chrome.driver=/usr/local/share/chrome_driver/chromedriver -- -port...

Have we tried bumping timeouts for the aspnetcore-components-e2e pipeline yet @sebastienros❔ Won't help if a test is just hanging but might work if we're just dealing w/ a general slowdown.

> I can try to bump to 2h to have an idea of how long it will take, but are we ok with that much carbon impact? Good question. In...

@SteveSandersonMS I'm fine w/ your timing _except_ for the likelihood Chrome gets updated to be incompatible w/ our Selenium versions other than `selenium-standalone`. Might be best to leave that change...

> @dougbu I take you are on point for this one? Yes, and I'm in no rush. The changes here represent a regression and caused me to reactivate a loc...

I'm adding loc comments and changing some of the strings in a draft PR. Will let the loc process create a new PR to resolve the conflicts. May need to...