|Dmitry Gozman bd8433ba49||2 days ago|
|common||2 days ago|
|installation-tests||2 days ago|
|playwright-android||2 months ago|
|playwright-chromium||9 months ago|
|playwright-core||6 months ago|
|playwright-electron||2 months ago|
|playwright-firefox||9 months ago|
|playwright-webkit||9 months ago|
|.gitignore||9 months ago|
|README.md||10 months ago|
|build_package.js||3 weeks ago|
npm installwith no arguments or installing from github.
NOTE As of May 20, 2020, the only exception is the
playwright-electronpackage that doesn't follow the pack and is published manually. This is due to it's pre-1.0 status.
To build a package that will be shipped to NPM, use
The script populates package folder with contents, and then uses
npm pack to archive the folder.
As of May 20, 2020,
//packages/build_package.js does the following:
playwright-internalto the subpackage (e.g.
package.jsonand puts it in the subpackage
browsers.jsonand puts it in the subpackage
npm packto pack the subpackage folder
playwright package and save result as
$ ./packages/build_package.js playwright ./playwright.tgz
To debug what files are put into the folder, use
--no-cleanup flag and inspect the package folder:
$ ./packages/build_package.js playwright ./playwright.tgz --no-cleanup $ ls ./packages/playwright # inspect the folder
To test packages, use
All package publishing happens exclusively over CI/CD using the
playwright-electronversion is pre-1.0.0 and thus managed separately. It's specified inside the
playwright-electronis published manually.
To publish a new version of
./build_package.js playwright-electron ./playwright-electron.tgz
npm publish playwright-electron.tgz