Uh oh!
There was an error while loading. Please reload this page.
chore(tests): Use verdaccio as node process instead of docker image - #20336
Conversation
size-limit report 📦
|
| - name: Check dependency cache | ||
| uses: actions/cache@v4 | ||
| uses: actions/cache@v5 |
There was a problem hiding this comment.
leftover I noticed I forgot to bump, not really related but this is non-breaking for us.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 64cbb91. Configure here.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…20336) Extracted out from #20270 This rewrites how we run verdaccio to run this as node process instead of via docker. For this, I pinned the latest verdaccio version in the e2e package, and run it via node APIs as a detached process. This also means no more docker requirement to run this stuff locally. Works both with `yarn test:run xxx` for local usage as well as with `yarn test:prepare` for CI usage.

Extracted out from #20270
This rewrites how we run verdaccio to run this as node process instead of via docker.
For this, I pinned the latest verdaccio version in the e2e package, and run it via node APIs as a detached process. This also means no more docker requirement to run this stuff locally. Works both with
yarn test:run xxxfor local usage as well as withyarn test:preparefor CI usage.