github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
f8cd6c4cce
puppeteer/package.json

118 lines
4.2 KiB
JSON
Raw Normal View History

Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
{
"name": "puppeteer",
chore: mark v5.4.1-post (#6553)
2020-10-27 16:07:36 +00:00
"version": "5.4.1-post",
Add .npmignore (#282)
2017-08-16 05:30:56 +00:00
"description": "A high-level API to control headless Chrome over the DevTools Protocol",
chore(agnostic): ship CJS and ESM builds (#6095) * chore(agnostic): ship CJS and ESM builds For our work to enable Puppeteer in other environments (e.g. a browser) we need to ship an ESM build. This commit changes our config to ship to `lib/cjs` and `lib/esm` accordingly. The majority of our code stays the same, with one small fix for the CJS build to ensure that we ship a version that lets you `require('puppeteer')` rather than have to `require('puppeteer').default`. We do this with the `cjs-entry.js` which is what the `main` field in our `package.json` points to. We also swap to `read-pkg-up` to find the `package.json` file. This is because the folder structure of `lib/` does not match `src/` now we ship to `cjs` and `esm`, so you cannot rely on exact paths. This module works up from the file to find the nearest `package.json` so it will always find Puppeteer's `package.json`. Note that we *do not* point any users to the ESM build. We happen to ship those files so people who know about them can get at them but it's not expected (nor will we actively support) that people will rely on them. The CommonJS build is considered our main build. We may make breaking changes to the structure of the ESM build which we will do without requiring new major versions. For example the ESM build currently ships all files that the CJS build does, but given we are working on the ESM build being able to run in the browser this may change over time. Long term once the Node versions catch up we can ditch CJS and ship exclusively ESM but we are not there yet.
2020-06-25 13:24:46 +00:00
"main": "./cjs-entry.js",
chore: update URLs (#5185)
2019-11-26 12:12:25 +00:00
"repository": "github:puppeteer/puppeteer",
Fix readme example
2017-06-19 22:01:14 +00:00
"engines": {
chore: drop Node.js v8 support (#5365) * chore: update relevant Node.js versions from 8 to 10 * chore: remove node6 and node8 folders from puppeteer-firefox ci * fix: loosen definition for proc.stdio * fix: update typescript version used in npm run test-types
2020-03-10 20:55:32 +00:00
"node": ">=10.18.1"
Fix readme example
2017-06-19 22:01:14 +00:00
},
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
"scripts": {
feat: add web test runner (#6200)
2020-07-22 11:14:35 +00:00
"test-browser": "wtr",
"test-browser-watch": "wtr --watch",
chore: enforce file extensions on imports (#6202) * chore: enforce file extensions on imports To make our output agnostic it should include file extensions in the output, as per the ESM spec. It's a bit odd for Node packages but makes it easier to publish a browser build.
2020-07-13 09:22:26 +00:00
"unit": "npm run tsc-cjs && mocha --config mocha-config/puppeteer-unit-tests.js",
chore: Remove target debug-unit and add unit-debug (#6411) * debug-unit is confusing * unit-debug runs all tests in debug mode
2020-09-11 08:10:25 +00:00
"unit-debug": "npm run tsc-cjs && mocha --inspect-brk --config mocha-config/puppeteer-unit-tests.js",
chore: update how we track coverage during unit tests (#5779) * chore: update how we track coverage during unit tests The old method of tracking coverage was causing issues. If a test failed on CI, that test's failure would be lost because the test failing would in turn cause the coverage to fail, but the `process.exit(1)` in the coverage code caused Mocha to not output anything useful. Instead the coverage checker now: * tracks the coverage in memory in a Map (this hasn't changed) * after all tests, writes that to disk in test/coverage.json (which is gitignored) * we then run a single Mocha test that asserts every method was called. This means if the test run fails, the build will fail and give the error about that test run, and that output won't be lost when the coverage then fails too. Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-30 12:00:41 +00:00
"unit-with-coverage": "cross-env COVERAGE=1 npm run unit",
"assert-unit-coverage": "cross-env COVERAGE=1 mocha --config mocha-config/coverage-tests.js",
chore: migrate unit tests to Mocha (#5600) Rather than maintain our own test runner we should instead lean on the community and use Mocha which is very popular and also our test runner of choice in DevTools too. Note that this commit doesn't remove the TestRunner source as it's still used for other unit tests, but they will be updated in a future PR and then we can remove the TestRunner. The main bulk of this PR is updating the tests as the old TestRunner passed in contextual data via the `it` function callback whereas Mocha does not, so we introduce some helpers for the tests to make it easier.
2020-04-09 05:56:25 +00:00
"funit": "PUPPETEER_PRODUCT=firefox npm run unit",
chore: remove npm run test-types call (#6447) It was an old script that doesn't exist any more.
2020-09-25 10:44:34 +00:00
"test": "npm run tsc && npm run lint --silent && npm run unit-with-coverage && npm run test-browser",
chore: fix installing from GitHub URL (#5669) The change to the install script to require TypeScript works fine when installing from npm (because on npm the `lib` directory with the compiled code already exists) but doesn't if you install from a GitHub URL. By default it seems npm uses the `files` list when you install from GitHub which means it's missing a bunch of files that we need to compile. Additionally by default when installing from a GitHub URL npm doesn't install the dependencies which is an issue for us when we need to compile TypeScript. The fix is to create a `prepare` script that runs TypeScript if required. From the npm docs [1]: > `prepare`: Run both BEFORE the package is packed and published, on > local npm install without any arguments, and when installing git > dependencies And from the npm docs on install [2], it confirms that if a package has a `prepare` script it is run when installing from GitHub: > As with regular git dependencies, dependencies and devDependencies > will be installed if the package has a prepare script, before the > package is done installing. Despite having the `prepare` script we still need the TypeScript check in `install.js` to satisfy the 3rd scenario below where we need to force a compile: * If I'm a user installing `puppeteer@X` from npm, the module is published with the `lib/` directory of compiled code, so I'm set. * If I'm a user installing Puppeteer from GitHub, the `prepare` script will run TypeScript for me so I'm set. * If I'm a developer working on Puppeteer, the `prepare` script also runs but _after_ `npm install` which means `install.js` fails as it requires `./lib/helper.js`. So in `install.js` we call `compileTypeScriptIfRequired` to catch this case. [1]: https://docs.npmjs.com/misc/scripts [2]: https://docs.npmjs.com/cli/install Co-authored-by: Mathias Bynens <mathias@qiwi.be> Fixes #5660.
2020-04-17 09:29:40 +00:00
"prepare": "node typescript-if-required.js",
chore: move code to src/ and emit with TypeScript (#5568) This updates our `tsconfig.json` so it emits our JavaScript files as well as type checking them. We compile into `./lib` which we then ship in our npm package. The source code has moved from `./lib` into `./src`. Because the `src/` directory is exclusively JS files, this change is a no-op in terms of code functionality but is the first step towards being able to replace `src/X.js` with `src/X.ts` in a way that allows us to migrate incrementally. The `lib` directory is gitignored, and the `src` directory is npmignored. On `npm publish` we will now run `npm run tsc` in order to generate the outputted code.
2020-04-02 14:25:19 +00:00
"prepublishOnly": "npm run tsc",
"dev-install": "npm run tsc && node install.js",
Add lint script and editorconfig file
2017-06-19 21:43:05 +00:00
"install": "node install.js",
chore: enforce consistent spacing around object curlys (#5700) The codebase was incredibly inconsistent with the use of spacing around curly braces, e.g.: ``` // this? const a = {b: 1} // or? const a = { b: 1 } ``` This extended into import statements also. Google's styleguide is no spacing, so we're going with that.
2020-04-21 09:40:04 +00:00
"eslint": "([ \"$CI\" = true ] && eslint --ext js --ext ts --quiet -f codeframe . || eslint --ext js --ext ts .)",
chore: add command to run eslint with `--fix` flag (#5829)
2020-05-07 13:54:33 +00:00
"eslint-fix": "eslint --ext js --ext ts --fix .",
chore: enforce Conventional Commits through commitlint (#6483) This patch sets up commitlint to enforce the Conventional Commits format. This check runs with the other lint checks as part of npm run lint, and a Git commit hook is set up via Husky for automated local checks. Issue: #6482
2020-10-08 10:04:15 +00:00
"commitlint": "commitlint --from=HEAD~1",
"lint": "npm run eslint && npm run tsc && npm run doc && npm run commitlint",
Implement public API coverage This patch: - implements a basic public API coverage based on 'helper.tracePublicAPI' methods - adds `npm run coverage` command which reports coverage after running all of the unit tests References #50.
2017-07-27 23:16:37 +00:00
"doc": "node utils/doclint/cli.js",
chore: clean `lib` when running tsc (#5982) I've had misleading type errors due to left over builds or tests behaving oddly. We should just strip the entire folder out before building again so there's no left over artefacts that could cause issues. The `|| true` in the command is so if `rm` errors because the folder doesn't exist, it doesn't exit with an error code.
2020-06-09 11:10:19 +00:00
"clean-lib": "rm -rf lib",
chore: automate publishing on new Git tags (#6536) Issues: #6482
2020-10-23 12:40:14 +00:00
"build": "npm run tsc",
chore(agnostic): ship CJS and ESM builds (#6095) * chore(agnostic): ship CJS and ESM builds For our work to enable Puppeteer in other environments (e.g. a browser) we need to ship an ESM build. This commit changes our config to ship to `lib/cjs` and `lib/esm` accordingly. The majority of our code stays the same, with one small fix for the CJS build to ensure that we ship a version that lets you `require('puppeteer')` rather than have to `require('puppeteer').default`. We do this with the `cjs-entry.js` which is what the `main` field in our `package.json` points to. We also swap to `read-pkg-up` to find the `package.json` file. This is because the folder structure of `lib/` does not match `src/` now we ship to `cjs` and `esm`, so you cannot rely on exact paths. This module works up from the file to find the nearest `package.json` so it will always find Puppeteer's `package.json`. Note that we *do not* point any users to the ESM build. We happen to ship those files so people who know about them can get at them but it's not expected (nor will we actively support) that people will rely on them. The CommonJS build is considered our main build. We may make breaking changes to the structure of the ESM build which we will do without requiring new major versions. For example the ESM build currently ships all files that the CJS build does, but given we are working on the ESM build being able to run in the browser this may change over time. Long term once the Node versions catch up we can ditch CJS and ship exclusively ESM but we are not there yet.
2020-06-25 13:24:46 +00:00
"tsc": "npm run clean-lib && tsc --version && npm run tsc-cjs && npm run tsc-esm",
chore: vendor Mitt & update project structure (#6209) * chore: vendor Mitt into src/common/third-party As discussed in #6203 we need to vendor our common dependencies in so that when we ship an ESM build all imports point to file paths and do not rely on Node resolution (e.g. a browser does not understand `import mitt from 'mitt'`).
2020-07-14 15:57:29 +00:00
"tsc-cjs": "tsc -b src/tsconfig.cjs.json",
"tsc-esm": "tsc -b src/tsconfig.esm.json",
chore: make sure Puppeteer bundling works (#3239) This patch: - adds "browser" field to the package.json with default bundling options. - introduces "bundle" and "unit-bundle" commands to create bundle and test bundle - starts running bundle tests on Travis Node 8 bots Fixes #2374.
2018-09-13 19:08:51 +00:00
"apply-next-version": "node utils/apply_next_version.js",
chore: Introduce API Extractor and start generating documentation (#5967)
2020-06-04 10:47:13 +00:00
"test-install": "scripts/test-install.sh",
chore: ensure new-docs are up to date (#5994) * chore: ensure new-docs are up to date This adds a Travis check that if we re-generate the docs we get the exact output (by checking if the Git tree is dirty). We do the dirty check by using `git status --porcelain`, seeing how many lines that outputs, and using that as the exit code (taking only the first 255 lines to avoid invalid exit codes). `--porcelain` makes the output be empty if the repo is not dirty in anyway which translates into an exit code of 0. We can't use `git diff-index --quiet HEAD` as it exits with 0 if there are untracked files in the repo but we want that to cause a failure.
2020-06-11 08:48:37 +00:00
"generate-docs": "npm run tsc && api-extractor run --local --verbose && api-documenter markdown -i temp -o new-docs",
chore: use devtools-protocol package (#6172) * chore: Use devtools-protocol package Rather than maintain our own protocol we can instead use the devtools-protocol package and pin it to the version of Chromium that Puppeteer is shipping with. The only changes are naming changes between the bespoke protocol that Puppeteer created and the devtools-protocol one.
2020-07-10 10:51:52 +00:00
"generate-dependency-graph": "echo 'Requires graphviz installed locally!' && depcruise --exclude 'api.ts' --do-not-follow '^node_modules' --output-type dot src/index.ts | dot -T png > dependency-chart.png",
chore: automate versioning + changelog (#6556) As long as we follow Conventional Commits for our commit messages (which is now enforced since #6483), we can automate the maintenance of this new changelog, which enables us to later automate the release process altogether. This patch also eliminates the versioning decision-making process by automating it based on our commit messages. Issue: #6482
2020-10-29 09:53:51 +00:00
"ensure-correct-devtools-protocol-revision": "ts-node -s scripts/ensure-correct-devtools-protocol-package",
"release": "standard-version"
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
},
chore: manage published files via `files` option (#5659) Rather than a denylist (`.npmignore`) we can instead use an allowlist via the `files` option in `package.json`. This makes it much harder to accidentally include files or folders in the build as you have to explicitly list the files that will be included. Fixes #5648.
2020-04-17 09:32:25 +00:00
"files": [
"lib/",
chore: add test for npm package installing correctly (#5714) * chore: add test for npm package installing correctly This command packs up the module and installs it again to check we're correctly bundling everything we need to allow users to do a fresh install. * install realpath
2020-04-22 14:33:36 +00:00
"install.js",
chore(agnostic): ship CJS and ESM builds (#6095) * chore(agnostic): ship CJS and ESM builds For our work to enable Puppeteer in other environments (e.g. a browser) we need to ship an ESM build. This commit changes our config to ship to `lib/cjs` and `lib/esm` accordingly. The majority of our code stays the same, with one small fix for the CJS build to ensure that we ship a version that lets you `require('puppeteer')` rather than have to `require('puppeteer').default`. We do this with the `cjs-entry.js` which is what the `main` field in our `package.json` points to. We also swap to `read-pkg-up` to find the `package.json` file. This is because the folder structure of `lib/` does not match `src/` now we ship to `cjs` and `esm`, so you cannot rely on exact paths. This module works up from the file to find the nearest `package.json` so it will always find Puppeteer's `package.json`. Note that we *do not* point any users to the ESM build. We happen to ship those files so people who know about them can get at them but it's not expected (nor will we actively support) that people will rely on them. The CommonJS build is considered our main build. We may make breaking changes to the structure of the ESM build which we will do without requiring new major versions. For example the ESM build currently ships all files that the CJS build does, but given we are working on the ESM build being able to run in the browser this may change over time. Long term once the Node versions catch up we can ditch CJS and ship exclusively ESM but we are not there yet.
2020-06-25 13:24:46 +00:00
"typescript-if-required.js",
chore: Don't store revisions in `package.json` (#6109) * 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.
2020-06-29 15:13:24 +00:00
"cjs-entry.js",
"cjs-entry-core.js"
chore: manage published files via `files` option (#5659) Rather than a denylist (`.npmignore`) we can instead use an allowlist via the `files` option in `package.json`. This makes it much harder to accidentally include files or folders in the build as you have to explicitly list the files that will be included. Fixes #5648.
2020-04-17 09:32:25 +00:00
],
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
"author": "The Chromium Authors",
correct license to be a valid SPDX license expression
2017-08-31 18:16:28 +00:00
"license": "Apache-2.0",
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
"dependencies": {
chore: update dependencies (#3526) Major updates are: - `ws` moved to major 6 - no breaking changes for us. - `eslint` updated to major 5 - adds support for object spread.
2018-11-09 23:32:20 +00:00
"debug": "^4.1.0",
feat(chromium): roll Chromium to r818858 (#6526) This corresponds to Chromium 88.0.4298.0. This roll includes: - DevTools: Wait for a frame before sending touch and wheel events https://chromium-review.googlesource.com/c/chromium/src/+/2437695
2020-10-27 17:15:31 +00:00
"devtools-protocol": "0.0.818844",
chore(deps): update extract-zip to version 2 (#5610) extract-zip removed support for callbacks and instead uses promises. Moreover, it has TypeScript support which allows us to remove the @types/extract-zip package. This update allows downstream users to remove their installation of mkdirp, which uses a vulnerable version of minimist. For more info, see https://github.com/maxogden/extract-zip/releases/tag/v2.0.0 Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-04-09 19:13:25 +00:00
"extract-zip": "^2.0.0",
chore: upgrade https-proxy-agent (#5243) https-proxy-agent requires agent-base, which currently monkey-patches the core `https` Node module, causing problems in unrelated code. The latest version of https-proxy-agent uses the latest version of agent-base which no longer does this monkey patching.
2019-12-11 14:40:22 +00:00
"https-proxy-agent": "^4.0.0",
chore(agnostification): split up launcher class (#6484) The `Launcher` class was serving two purposes: 1. Launch browsers 2. Connect to browsers Number 1) only needs to be done in Node land, but 2) is agnostic; in a browser version of Puppeteer we'll need the ability to connect over a websocket to send commands back and forth. As part of the agnostification work we needed to split the `Launcher` up so that the connection part can be made agnostic. Additionally, I removed dependencies on `https`, `http` and `URL` from Node, instead leaning on fetch (via `node-fetch` if in Node land) and the browser `URL` API (which was added to Node in Node 10).
2020-10-12 09:08:57 +00:00
"node-fetch": "^2.6.1",
chore: Don't store revisions in `package.json` (#6109) * 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.
2020-06-29 15:13:24 +00:00
"pkg-dir": "^4.2.0",
chore: update dependencies (#3526) Major updates are: - `ws` moved to major 6 - no breaking changes for us. - `eslint` updated to major 5 - adds support for object spread.
2018-11-09 23:32:20 +00:00
"progress": "^2.0.1",
Adding proxy support for ChromiumDownloader (#455) This patch teaches puppeteer to download chromium over the HTTP proxy, if any. Fixes #448.
2017-08-23 15:33:29 +00:00
"proxy-from-env": "^1.0.0",
chore: bump rimraf to v3.0.2 (#5431) `rimraf` version 3.0.2 doesn't throw any more when used in Jest environment. Fixes #5425
2020-03-12 21:17:47 +00:00
"rimraf": "^3.0.2",
(feat) Add option to fetch Firefox Nightly (#5467) * (feat) Add option to fetch Firefox Nightly Add Firefox support to BrowserFetcher and the install script. By default, the latest Firefox Nightly is downloaded directly from archive.mozilla.org (dmg, tar.bz2 and zip) This also required changes that impact `puppeteer.launch()` and `puppeteer.executablePath()` Fixes #5151 * Update docs/api.md Co-Authored-By: Mathias Bynens <mathias@qiwi.be> * Clean up revision promise * Improve error handling in revision check * Remove matchAll * Use explicit octal mode * Update .gitignore Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-03-10 20:59:03 +00:00
"tar-fs": "^2.0.0",
"unbzip2-stream": "^1.3.3",
chore: update ws library (#5638) Updates `ws` and `@types/ws` to version 7. The breaking changes in version 7 are not ones that impact this project [1]. [1]: https://github.com/websockets/ws/releases/tag/7.0.0
2020-04-14 14:13:38 +00:00
"ws": "^7.2.3"
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
},
Add minimal test framework This patch adds some minimal tests for puppeteer's Page using Jasmine.
2017-05-12 23:36:37 +00:00
"devDependencies": {
chore: enforce Conventional Commits through commitlint (#6483) This patch sets up commitlint to enforce the Conventional Commits format. This check runs with the other lint checks as part of npm run lint, and a Git commit hook is set up via Husky for automated local checks. Issue: #6482
2020-10-08 10:04:15 +00:00
"@commitlint/cli": "^11.0.0",
"@commitlint/config-conventional": "^11.0.0",
chore: bump misc dependencies (#6488) This commit updates some miscellaneous dependencies to their latest versions (with no other changes required) and also removes the `browser` section, which was used by Browserify for the now long gone Puppeteer-Web package that we used to publish.
2020-10-08 15:02:37 +00:00
"@microsoft/api-documenter": "7.9.7",
"@microsoft/api-extractor": "7.10.4",
chore: update dependencies (#3526) Major updates are: - `ws` moved to major 6 - no breaking changes for us. - `eslint` updated to major 5 - adds support for object spread.
2018-11-09 23:32:20 +00:00
"@types/debug": "0.0.31",
chore(deps): bump dependencies (#2397) Fixes #2394
2018-04-17 21:51:03 +00:00
"@types/mime": "^2.0.0",
chore: migrate tests to TypeScript (#6075) This CL migrates all the tests to TypeScript. The main benefits of this is that we start consuming our TypeScript definitions and therefore find errors in them. The act of migrating found some bugs in our definitions and now we can be sure to avoid them going forwards. You'll notice the addition of some `TODO`s in the code; I didn't want this CL to get any bigger than it already is but I intend to follow those up once this lands. It's mostly figuring out how to extend the `expect` types with our `toBeGolden` helpers and some other slight confusions with types that the tests exposed. Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-06-23 05:18:46 +00:00
"@types/mocha": "^7.0.2",
"@types/node": "^14.0.13",
chore: add @types/proxy-from-env (#5831)
2020-05-07 16:26:26 +00:00
"@types/proxy-from-env": "^1.0.1",
chore: Use Typescript to lint JSDoc annotations (#986) This patch starts using typescript to lint JSDoc annotations. Note: this uses typescript's bleeding edge. We should migrate to stable once it has all the necessary bugfixes. References #65.
2017-10-10 05:31:40 +00:00
"@types/rimraf": "^2.0.2",
feat: page.waitForTimeout (#6268)
2020-07-28 08:37:49 +00:00
"@types/sinon": "^9.0.4",
(feat) Add option to fetch Firefox Nightly (#5467) * (feat) Add option to fetch Firefox Nightly Add Firefox support to BrowserFetcher and the install script. By default, the latest Firefox Nightly is downloaded directly from archive.mozilla.org (dmg, tar.bz2 and zip) This also required changes that impact `puppeteer.launch()` and `puppeteer.executablePath()` Fixes #5151 * Update docs/api.md Co-Authored-By: Mathias Bynens <mathias@qiwi.be> * Clean up revision promise * Improve error handling in revision check * Remove matchAll * Use explicit octal mode * Update .gitignore Co-authored-by: Mathias Bynens <mathias@qiwi.be>
2020-03-10 20:59:03 +00:00
"@types/tar-fs": "^1.16.2",
chore: update ws library (#5638) Updates `ws` and `@types/ws` to version 7. The breaking changes in version 7 are not ones that impact this project [1]. [1]: https://github.com/websockets/ws/releases/tag/7.0.0
2020-04-14 14:13:38 +00:00
"@types/ws": "^7.2.4",
chore: update eslint & eslint plugins (#6487) Updates ESLint, the TypeScript ESLint plugins, and updates code where the rules have changed.
2020-10-12 09:30:35 +00:00
"@typescript-eslint/eslint-plugin": "^4.4.0",
"@typescript-eslint/parser": "^4.4.0",
chore(agnostification): common/helper.ts (#6515) * chore(agnostification): common/helper.ts The `readProtocolStream` method uses `fs` only if you want to write to a file. So we gate at the start of the function and ensure that if we got given a path we are not in a Node environment.
2020-10-19 08:57:15 +00:00
"@web/test-runner": "^0.9.2",
chore: update dependencies (#3526) Major updates are: - `ws` moved to major 6 - no breaking changes for us. - `eslint` updated to major 5 - adds support for object spread.
2018-11-09 23:32:20 +00:00
"commonmark": "^0.28.1",
chore: bump misc dependencies (#6488) This commit updates some miscellaneous dependencies to their latest versions (with no other changes required) and also removes the `browser` section, which was used by Browserify for the now long gone Puppeteer-Web package that we used to publish.
2020-10-08 15:02:37 +00:00
"cross-env": "^7.0.2",
chore: add dependency chart generation as script (#6034)
2020-06-17 13:29:39 +00:00
"dependency-cruiser": "^9.7.0",
chore: update eslint & eslint plugins (#6487) Updates ESLint, the TypeScript ESLint plugins, and updates code where the rules have changed.
2020-10-12 09:30:35 +00:00
"eslint": "^7.10.0",
"eslint-config-prettier": "^6.12.0",
chore: enforce file extensions on imports (#6202) * chore: enforce file extensions on imports To make our output agnostic it should include file extensions in the output, as per the ESM spec. It's a bit odd for Node packages but makes it easier to publish a browser build.
2020-07-13 09:22:26 +00:00
"eslint-plugin-import": "^2.22.0",
chore: update eslint & eslint plugins (#6487) Updates ESLint, the TypeScript ESLint plugins, and updates code where the rules have changed.
2020-10-12 09:30:35 +00:00
"eslint-plugin-mocha": "^8.0.0",
"eslint-plugin-prettier": "^3.1.4",
"eslint-plugin-unicorn": "^22.0.0",
Implement documentation linter (#47) This patch implements documentation linter, which leaves under `test/doclint` folder. The documentation linter works like this: 1. Parse javascript source code with esprima and construct a "documentation" out of source code 2. Generate HTML out of `api.md` and traverse the HTML with puppeteer. 3. Make sure javascript aligns nicely with HTML The documentation linter adds the following commands: - `yarn doc` - to test that documentation covers all the relevant apis - `yarn generate-toc` - to update the table-of-contents for the `api.md`
2017-07-07 16:36:45 +00:00
"esprima": "^4.0.0",
chore: Use expect for assertions (#5581) Rather than use our own custom expect library, we can use expect from npm [1], which has an API almost identical to the one Puppeteer has, but with more options, better diffing, and is used by many in the community as it's the default assertions library that comes with Jest. It's also thoroughly documented [2]. [1]: https://www.npmjs.com/package/expect [2]: https://jestjs.io/docs/en/expect
2020-04-03 11:22:55 +00:00
"expect": "^25.2.7",
chore: enforce Conventional Commits through commitlint (#6483) This patch sets up commitlint to enforce the Conventional Commits format. This check runs with the other lint checks as part of npm run lint, and a Git commit hook is set up via Husky for automated local checks. Issue: #6482
2020-10-08 10:04:15 +00:00
"husky": "^4.3.0",
chore: update pngjs to 5.0.0 and jpeg-js to 0.3.7 (#5676)
2020-04-23 09:38:00 +00:00
"jpeg-js": "^0.3.7",
fix: add mime dependency back to fix build (#6441) * Added back dependency `"mime": "^2.0.3",` to fix build; * Previous builds passed because of the node package caching.
2020-09-23 07:56:40 +00:00
"mime": "^2.0.3",
Introduce screenshot tests This patch introduces a goldentest.js. The tests inside the file should rely on "golden" results rather then asserts. For now, goldentest.js allows only image expectations. If the actual result doesn't match the expected result, the two files are created under `test/output` folder: - The '-actual.png' contains the actual test result - The '-diff.png' contains the diff between images
2017-06-16 21:33:34 +00:00
"minimist": "^1.2.0",
chore: fix travis config (#6537)
2020-10-22 13:37:28 +00:00
"mocha": "^8.2.0",
Introduce screenshot tests This patch introduces a goldentest.js. The tests inside the file should rely on "golden" results rather then asserts. For now, goldentest.js allows only image expectations. If the actual result doesn't match the expected result, the two files are created under `test/output` folder: - The '-actual.png' contains the actual test result - The '-diff.png' contains the diff between images
2017-06-16 21:33:34 +00:00
"ncp": "^2.0.0",
add missing pngjs module
2017-06-16 22:02:14 +00:00
"pixelmatch": "^4.0.2",
chore: update pngjs to 5.0.0 and jpeg-js to 0.3.7 (#5676)
2020-04-23 09:38:00 +00:00
"pngjs": "^5.0.0",
chore: update eslint & eslint plugins (#6487) Updates ESLint, the TypeScript ESLint plugins, and updates code where the rules have changed.
2020-10-12 09:30:35 +00:00
"prettier": "^2.1.2",
Warn when given unsupported product name. (#5845) * Warn when given unsupported product name. Fixes #5844. This change means when a user launches Puppeteer with a product name that is not supported (which at the time of this commit means it's not `firefox` or `chrome) we will warn them about it. Decided on just a warning vs an error because the current behaviour is that we fallback to launching Chrome and I don't think this warrants a breaking change.
2020-05-12 09:30:24 +00:00
"sinon": "^9.0.2",
chore: automate versioning + changelog (#6556) As long as we follow Conventional Commits for our commit messages (which is now enforced since #6483), we can automate the maintenance of this new changelog, which enables us to later automate the release process altogether. This patch also eliminates the versioning decision-making process by automating it based on our commit messages. Issue: #6482
2020-10-29 09:53:51 +00:00
"standard-version": "^9.0.0",
chore: Use Typescript to lint JSDoc annotations (#986) This patch starts using typescript to lint JSDoc annotations. Note: this uses typescript's bleeding edge. We should migrate to stable once it has all the necessary bugfixes. References #65.
2017-10-10 05:31:40 +00:00
"text-diff": "^1.0.1",
chore: bump misc dependencies (#6488) This commit updates some miscellaneous dependencies to their latest versions (with no other changes required) and also removes the `browser` section, which was used by Browserify for the now long gone Puppeteer-Web package that we used to publish.
2020-10-08 15:02:37 +00:00
"ts-node": "^9.0.0",
chore: fix ESLint violation and lessen rule strictness (#6081)
2020-06-23 11:55:42 +00:00
"typescript": "3.9.5"
chore: make sure Puppeteer bundling works (#3239) This patch: - adds "browser" field to the package.json with default bundling options. - introduces "bundle" and "unit-bundle" commands to create bundle and test bundle - starts running bundle tests on Travis Node 8 bots Fixes #2374.
2018-09-13 19:08:51 +00:00
},
chore: enforce Conventional Commits through commitlint (#6483) This patch sets up commitlint to enforce the Conventional Commits format. This check runs with the other lint checks as part of npm run lint, and a Git commit hook is set up via Husky for automated local checks. Issue: #6482
2020-10-08 10:04:15 +00:00
"husky": {
"hooks": {
"commit-msg": "commitlint --env HUSKY_GIT_PARAMS"
}
chore: automate versioning + changelog (#6556) As long as we follow Conventional Commits for our commit messages (which is now enforced since #6483), we can automate the maintenance of this new changelog, which enables us to later automate the release process altogether. This patch also eliminates the versioning decision-making process by automating it based on our commit messages. Issue: #6482
2020-10-29 09:53:51 +00:00
},
"standard-version": {
"skip": {
"commit": true,
"tag": true
}
Puppeteer: staging commit.
2017-05-11 07:06:41 +00:00
}
}
Reference in New Issue Copy Permalink