puppeteer/packages/puppeteer-core/third_party/tsconfig.cjs.json

{
  "extends": "../../../tsconfig.base.json",
  "compilerOptions": {
    "module": "NodeNext",
    "moduleResolution": "NodeNext",
    "outDir": "../lib/cjs/third_party",
    "declarationMap": false,
    "sourceMap": false
  }
}
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			`{`
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: 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			`"compilerOptions": {`
chore: update dependencies (#10785) 2023-08-28 11:01:52 +00:00			`"module": "NodeNext",`
			`"moduleResolution": "NodeNext",`
chore: use wireit from workspace scripts (#9659) 2023-02-13 14:50:44 +00:00			`"outDir": "../lib/cjs/third_party",`
chore: update dependencies (#10785) 2023-08-28 11:01:52 +00:00			`"declarationMap": false,`
chore: bundle vendor code (#9016) This PR removes the manual vendoring process. Third party code can now be updated using the typical NPM pipeline with types/code bundling done through Rollup. 2022-09-28 11:03:19 +00:00			`"sourceMap": false`
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			`}`
			`}`