puppeteer/tools/tsconfig.json

{
  "extends": "../tsconfig.base.json",
  "files": ["../package.json"]
}
chore(agnostic): Remove use of util.promisify (#6446) In `src/common` we now use `fs.promises.X` which we can dynamically `import`. In a browser environment this code will never run because it's gated on `isNode` (in a future PR we will add tree-shaking to the bundle step such that this code is eliminated). By using `import`, we ensure TypeScript still can track types and give good type information. In `src/node` we continue to use `util.promisify` but that's not a concern as that code explicitly is never run in the browser. 2020-09-28 09:35:35 +00:00			`{`
feat: separate puppeteer and puppeteer-core (#9023) This PR moves the puppeteer source code into separate mono-repo packages: - `puppeteer` and `puppeteer-core` are now separated into their own packages. - `puppeteer-core` has a new exports called `puppeteer-core/internal` for internal usage. Tests and various tools have been updated to accommodate the migration. 2022-10-05 12:17:03 +00:00			`"extends": "../tsconfig.base.json",`
chore(deps-dev): Bump the dev-dependencies group with 13 updates (#11908) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Nikolay Vitkov <nvitkov@chromium.org> 2024-02-14 18:20:12 +00:00			`"files": ["../package.json"]`
chore(agnostic): Remove use of util.promisify (#6446) In `src/common` we now use `fs.promises.X` which we can dynamically `import`. In a browser environment this code will never run because it's gated on `isNode` (in a future PR we will add tree-shaking to the bundle step such that this code is eliminated). By using `import`, we ensure TypeScript still can track types and give good type information. In `src/node` we continue to use `util.promisify` but that's not a concern as that code explicitly is never run in the browser. 2020-09-28 09:35:35 +00:00			`}`
No results found.