1f5e333f00
* chore: Don't store revisions in `package.json` It's quite messy to have to require the `package.json` file in multiple places purely to find out what revision of a given browser we want to use. We can also achieve better type safety by placing it in an actual source file. This commit makes that change and also tidies up our reliance on `package.json` within the source code generally; we now only use it to find the location of the Puppeteer root such that we know where to install downloaded browsers to. To avoid using `package.json` to parse the name of the module, we also now explicitly have an entry point for the Puppeteer module and the Puppeter Core module. This will make it easier in the future to ship less code as part of core (e.g. core never needs to download a browser, so why ship that code?). Core can also then not have any revisions based info contained in it. The test install script has also been updated to ensure that puppeteer-core can be installed correctly too. Finally, the `install` script has been moved to TypeScript for nicer typechecking and safety. The functionality of it has not changed.
21 lines
303 B
Plaintext
21 lines
303 B
Plaintext
/node_modules/
|
|
/test/output-chromium
|
|
/test/output-firefox
|
|
/test/test-user-data-dir*
|
|
/.local-chromium/
|
|
/.local-firefox/
|
|
/.dev_profile*
|
|
.DS_Store
|
|
*.swp
|
|
*.pyc
|
|
.vscode
|
|
package-lock.json
|
|
yarn.lock
|
|
/node6
|
|
/utils/browser/puppeteer-web.js
|
|
/lib
|
|
test/coverage.json
|
|
temp/
|
|
dependency-chart.png
|
|
puppeteer-core-*.tgz
|