-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: follow-up with ffmpeg downloads to registry #5278
Labels
Comments
aslushnikov
added a commit
to aslushnikov/playwright
that referenced
this issue
Feb 4, 2021
aslushnikov
added a commit
that referenced
this issue
Feb 4, 2021
aslushnikov
added a commit
to aslushnikov/playwright
that referenced
this issue
Feb 4, 2021
Drive-By: update `//utils/roll_browser.js` script to support FFMPEG References microsoft#5278
aslushnikov
added a commit
that referenced
this issue
Feb 4, 2021
Drive-By: update `//utils/roll_browser.js` script to support FFMPEG References #5278
aslushnikov
added a commit
to aslushnikov/playwright
that referenced
this issue
Feb 4, 2021
This patch: - inlines `packagePath` into `PlaywrightOptions` - renames `browserPaths.browsersPath` to `browserPaths.registryPath` to avoid confusion. All `browsersPath` variables are renamed to `registryPath` too. - introduces a single `browserPaths.resolvePaths()` method that resolves all paths given only `packagePath` and browser descriptor. Fixes microsoft#5278
aslushnikov
added a commit
to aslushnikov/playwright
that referenced
this issue
Feb 5, 2021
This patch introduces a new Registry class that incapsulates all logic regarding browsers and their paths. Fixes microsoft#5278
aslushnikov
added a commit
that referenced
this issue
Feb 9, 2021
This patch introduces a new Registry class that incapsulates all logic regarding browsers and their paths. Fixes #5278
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
packagePath
var toplaywrightOptions
The text was updated successfully, but these errors were encountered: