microsoft/playwright
1
1
Fork 0
mirror of https://github.com/microsoft/playwright.git synced 2024-12-15 06:02:57 +03:00
Code Issues Projects Releases Wiki Activity
243ede5dfb
playwright/browsers.json

34 lines
648 B
JSON
Raw Normal View History

chore: read browser revisions off browsers.json (#2009)
2020-04-28 20:37:23 +03:00
{
chore: generate protocol during browser roll (#2719) We now commit protocol.ts files during the roll. New utils/roll_browser.js helps with that. This makes our installation very shallow: - build installer; - download browsers.
2020-07-02 01:22:29 +03:00
"comment": "Do not edit this file, use utils/roll_browser.js",
chore: read browser revisions off browsers.json (#2009)
2020-04-28 20:37:23 +03:00
"browsers": [
{
"name": "chromium",
feat(chromium): roll to r869727 (#6170) Fixes #5952 Fixes #6016
2021-04-10 06:57:41 +03:00
"revision": "869727",
fix(installer): retain browsers installed via Playwrigth CLI (#5904) Browser registry is responsible for 3 things: 1. Remove downloaded browsers if there are no packages that refer to them 2. Install default browsers needed for the current package 3. Install browsers on-demand when used through Playwright CLI Currently, registry relies on a single "download" field in `browsers.json` to carry both (1) and (2). However, browsers in (3) are marked as `download: false` so that they aren't installed automatically in (2), so auto-remove procedure in (1) removes them on subsequent installation. One possible approach to fix this would be modifying package's `browsers.json` to change `download: false` to `true` when browsers are installed with Playwright CLI. This approach was explored here: https://github.com/microsoft/playwright/commit/bc04a51800d6d6322e43b7d147fc0ec42181e084 We decided against this since we have a history of issues related to package modifications after NPM installation. This breaks all sorts of yarn/npm caching mechanisms. Instead, this patch is a two-step refactor: - remove the "download" field in `browsers.json`. Now, all registries (including old ones from previously-released versions) will retain any browsers that are mentioned in the `browsers.json`. - add a new flag "installByDefault", that is **only used** for default installation. With this change, the registry tasks are done like this: - (1) auto-removal: if browser has a back reference, it is retained, otherwise it is removed from registry - (2) default installation: use only `installByDefault` to carry default installations - (3) CLI installation: simply installs browsers. Since we retain everythings that's referenced in (1), browsers aren't removed. Fixes #5902
2021-03-22 21:43:29 +03:00
"installByDefault": true
chore: read browser revisions off browsers.json (#2009)
2020-04-28 20:37:23 +03:00
},
{
"name": "firefox",
fea(firefox): roll Firefox to r1245 (#6114) Just a healthy roll.
2021-04-07 18:04:52 +03:00
"revision": "1245",
fix(installer): retain browsers installed via Playwrigth CLI (#5904) Browser registry is responsible for 3 things: 1. Remove downloaded browsers if there are no packages that refer to them 2. Install default browsers needed for the current package 3. Install browsers on-demand when used through Playwright CLI Currently, registry relies on a single "download" field in `browsers.json` to carry both (1) and (2). However, browsers in (3) are marked as `download: false` so that they aren't installed automatically in (2), so auto-remove procedure in (1) removes them on subsequent installation. One possible approach to fix this would be modifying package's `browsers.json` to change `download: false` to `true` when browsers are installed with Playwright CLI. This approach was explored here: https://github.com/microsoft/playwright/commit/bc04a51800d6d6322e43b7d147fc0ec42181e084 We decided against this since we have a history of issues related to package modifications after NPM installation. This breaks all sorts of yarn/npm caching mechanisms. Instead, this patch is a two-step refactor: - remove the "download" field in `browsers.json`. Now, all registries (including old ones from previously-released versions) will retain any browsers that are mentioned in the `browsers.json`. - add a new flag "installByDefault", that is **only used** for default installation. With this change, the registry tasks are done like this: - (1) auto-removal: if browser has a back reference, it is retained, otherwise it is removed from registry - (2) default installation: use only `installByDefault` to carry default installations - (3) CLI installation: simply installs browsers. Since we retain everythings that's referenced in (1), browsers aren't removed. Fixes #5902
2021-03-22 21:43:29 +03:00
"installByDefault": true
chore: read browser revisions off browsers.json (#2009)
2020-04-28 20:37:23 +03:00
},
{
"name": "webkit",
feat(webkit): bump to 1463 (#6210)
2021-04-16 21:56:03 +03:00
"revision": "1463",
fix(installer): retain browsers installed via Playwrigth CLI (#5904) Browser registry is responsible for 3 things: 1. Remove downloaded browsers if there are no packages that refer to them 2. Install default browsers needed for the current package 3. Install browsers on-demand when used through Playwright CLI Currently, registry relies on a single "download" field in `browsers.json` to carry both (1) and (2). However, browsers in (3) are marked as `download: false` so that they aren't installed automatically in (2), so auto-remove procedure in (1) removes them on subsequent installation. One possible approach to fix this would be modifying package's `browsers.json` to change `download: false` to `true` when browsers are installed with Playwright CLI. This approach was explored here: https://github.com/microsoft/playwright/commit/bc04a51800d6d6322e43b7d147fc0ec42181e084 We decided against this since we have a history of issues related to package modifications after NPM installation. This breaks all sorts of yarn/npm caching mechanisms. Instead, this patch is a two-step refactor: - remove the "download" field in `browsers.json`. Now, all registries (including old ones from previously-released versions) will retain any browsers that are mentioned in the `browsers.json`. - add a new flag "installByDefault", that is **only used** for default installation. With this change, the registry tasks are done like this: - (1) auto-removal: if browser has a back reference, it is retained, otherwise it is removed from registry - (2) default installation: use only `installByDefault` to carry default installations - (3) CLI installation: simply installs browsers. Since we retain everythings that's referenced in (1), browsers aren't removed. Fixes #5902
2021-03-22 21:43:29 +03:00
"installByDefault": true,
devops: start downloading webkit fork on Mac 10.14 (#5837) References #5833
2021-03-17 19:34:09 +03:00
"revisionOverrides": {
"mac10.14": "1443"
}
devops: downloading ffmpeg during install step (#5249) This patch starts downloading FFMPEG like we download our browsers instead of bundling it in the NPM package. With this patch, NPM size is reduced from 8.8MB to 1.7MB. Consequences: - `npx playwright` is drastically faster now - playwright driver for language bindings is way smaller - projects that bundle Playwright can pass Apple Notorization Fixes #5193
2021-02-03 20:19:11 +03:00
},
feat: support webkit technology preview (#5885) This patch adds support for `technology preview` webkit channel, which we will keep close to the actual Safari Technology Preview releases. This channel does not install by default. It is supposed to be installed with the following CLI command: ```sh $ npx playwright install webkit-technology-preview ``` Once the channel is installed, it can be used the following way: ```js const browser = await playwright.webkit.launch({ channel: 'technology-preview', }); ``` **NOTE:** if clients attempt using the channel without installing it, it'll throw an error with a copyable instructions to install via CLI. References #5884
2021-03-31 21:32:10 +03:00
{
"name": "webkit-technology-preview",
"revision": "1443",
"installByDefault": false
},
devops: downloading ffmpeg during install step (#5249) This patch starts downloading FFMPEG like we download our browsers instead of bundling it in the NPM package. With this patch, NPM size is reduced from 8.8MB to 1.7MB. Consequences: - `npx playwright` is drastically faster now - playwright driver for language bindings is way smaller - projects that bundle Playwright can pass Apple Notorization Fixes #5193
2021-02-03 20:19:11 +03:00
{
"name": "ffmpeg",
feat(ffmpeg): roll FFMPEG to r1005 (#5303) Drive-By: update `//utils/roll_browser.js` script to support FFMPEG References #5278
2021-02-04 08:15:09 +03:00
"revision": "1005",
fix(installer): retain browsers installed via Playwrigth CLI (#5904) Browser registry is responsible for 3 things: 1. Remove downloaded browsers if there are no packages that refer to them 2. Install default browsers needed for the current package 3. Install browsers on-demand when used through Playwright CLI Currently, registry relies on a single "download" field in `browsers.json` to carry both (1) and (2). However, browsers in (3) are marked as `download: false` so that they aren't installed automatically in (2), so auto-remove procedure in (1) removes them on subsequent installation. One possible approach to fix this would be modifying package's `browsers.json` to change `download: false` to `true` when browsers are installed with Playwright CLI. This approach was explored here: https://github.com/microsoft/playwright/commit/bc04a51800d6d6322e43b7d147fc0ec42181e084 We decided against this since we have a history of issues related to package modifications after NPM installation. This breaks all sorts of yarn/npm caching mechanisms. Instead, this patch is a two-step refactor: - remove the "download" field in `browsers.json`. Now, all registries (including old ones from previously-released versions) will retain any browsers that are mentioned in the `browsers.json`. - add a new flag "installByDefault", that is **only used** for default installation. With this change, the registry tasks are done like this: - (1) auto-removal: if browser has a back reference, it is retained, otherwise it is removed from registry - (2) default installation: use only `installByDefault` to carry default installations - (3) CLI installation: simply installs browsers. Since we retain everythings that's referenced in (1), browsers aren't removed. Fixes #5902
2021-03-22 21:43:29 +03:00
"installByDefault": true
chore: read browser revisions off browsers.json (#2009)
2020-04-28 20:37:23 +03:00
}
]
}
Reference in New Issue Copy Permalink