chore(main): release 14.2.0

.editorconfig

@@ -0,0 +1,9 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

.eslintignore

@@ -0,0 +1,17 @@
+test/assets/modernizr.js
+third_party/*
+utils/browser/puppeteer-web.js
+utils/doclint/check_public_api/test/
+node6/*
+node6-test/*
+experimental/
+lib/
+/index.d.ts
+# We ignore this file because it uses ES imports which we don't yet use
+# in the Puppeteer src, so it trips up the ESLint-TypeScript parser.
+utils/doclint/generate_types/test/test.ts
+vendor/
+web-test-runner.config.mjs
+test-ts-types/
+website/
+docs-dist/

.eslintrc.js

@@ -0,0 +1,190 @@
+module.exports = {
+  root: true,
+  env: {
+    node: true,
+    es6: true,
+  },
+
+  parser: '@typescript-eslint/parser',
+
+  plugins: ['mocha', '@typescript-eslint', 'unicorn', 'import'],
+
+  extends: ['plugin:prettier/recommended'],
+
+  rules: {
+    // Error if files are not formatted with Prettier correctly.
+    'prettier/prettier': 2,
+    // syntax preferences
+    quotes: [
+      2,
+      'single',
+      {
+        avoidEscape: true,
+        allowTemplateLiterals: true,
+      },
+    ],
+    'spaced-comment': [
+      2,
+      'always',
+      {
+        markers: ['*'],
+      },
+    ],
+    eqeqeq: [2],
+    'accessor-pairs': [
+      2,
+      {
+        getWithoutSet: false,
+        setWithoutGet: false,
+      },
+    ],
+    'new-parens': 2,
+    'func-call-spacing': 2,
+    'prefer-const': 2,
+
+    'max-len': [
+      2,
+      {
+        /* this setting doesn't impact things as we use Prettier to format
+         * our code and hence dictate the line length.
+         * Prettier aims for 80 but sometimes makes the decision to go just
+         * over 80 chars as it decides that's better than wrapping. ESLint's
+         * rule defaults to 80 but therefore conflicts with Prettier. So we
+         * set it to something far higher than Prettier would allow to avoid
+         * it causing issues and conflicting with Prettier.
+         */
+        code: 200,
+        comments: 90,
+        ignoreTemplateLiterals: true,
+        ignoreUrls: true,
+        ignoreStrings: true,
+        ignoreRegExpLiterals: true,
+      },
+    ],
+    // anti-patterns
+    'no-var': 2,
+    'no-with': 2,
+    'no-multi-str': 2,
+    'no-caller': 2,
+    'no-implied-eval': 2,
+    'no-labels': 2,
+    'no-new-object': 2,
+    'no-octal-escape': 2,
+    'no-self-compare': 2,
+    'no-shadow-restricted-names': 2,
+    'no-cond-assign': 2,
+    'no-debugger': 2,
+    'no-dupe-keys': 2,
+    'no-duplicate-case': 2,
+    'no-empty-character-class': 2,
+    'no-unreachable': 2,
+    'no-unsafe-negation': 2,
+    radix: 2,
+    'valid-typeof': 2,
+    'no-unused-vars': [
+      2,
+      {
+        args: 'none',
+        vars: 'local',
+        varsIgnorePattern:
+          '([fx]?describe|[fx]?it|beforeAll|beforeEach|afterAll|afterEach)',
+      },
+    ],
+    'no-implicit-globals': [2],
+
+    // es2015 features
+    'require-yield': 2,
+    'template-curly-spacing': [2, 'never'],
+
+    // ensure we don't have any it.only or describe.only in prod
+    'mocha/no-exclusive-tests': 'error',
+
+    // enforce the variable in a catch block is named error
+    'unicorn/catch-error-name': 'error',
+
+    'no-restricted-imports': [
+      'error',
+      {
+        patterns: ['*Events'],
+        paths: [
+          {
+            name: 'mitt',
+            message:
+              'Import Mitt from the vendored location: vendor/mitt/src/index.js',
+          },
+        ],
+      },
+    ],
+    'import/extensions': ['error', 'ignorePackages'],
+  },
+  overrides: [
+    {
+      files: ['*.ts'],
+      extends: [
+        'plugin:@typescript-eslint/eslint-recommended',
+        'plugin:@typescript-eslint/recommended',
+      ],
+      rules: {
+        'no-unused-vars': 0,
+        '@typescript-eslint/no-unused-vars': [
+          'error',
+          { argsIgnorePattern: '^_' },
+        ],
+        'func-call-spacing': 0,
+        '@typescript-eslint/func-call-spacing': 2,
+        semi: 0,
+        '@typescript-eslint/semi': 2,
+        '@typescript-eslint/no-empty-function': 0,
+        '@typescript-eslint/no-use-before-define': 0,
+        // We have to use any on some types so the warning isn't valuable.
+        '@typescript-eslint/no-explicit-any': 0,
+        // We don't require explicit return types on basic functions or
+        // dummy functions in tests, for example
+        '@typescript-eslint/explicit-function-return-type': 0,
+        // We know it's bad and use it very sparingly but it's needed :(
+        '@typescript-eslint/ban-ts-ignore': 0,
+        // We allow non-null assertions if the value was asserted using `assert` API.
+        '@typescript-eslint/no-non-null-assertion': 0,
+        /**
+         * This is the default options (as per
+         * https://github.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/docs/rules/ban-types.md),
+         *
+         * Unfortunately there's no way to
+         */
+        '@typescript-eslint/ban-types': [
+          'error',
+          {
+            extendDefaults: true,
+            types: {
+              /*
+               * Puppeteer's API accepts generic functions in many places so it's
+               * not a useful linting rule to ban the `Function` type. This turns off
+               * the banning of the `Function` type which is a default rule.
+               */
+              Function: false,
+            },
+          },
+        ],
+        '@typescript-eslint/array-type': [
+          2,
+          {
+            default: 'array-simple',
+          },
+        ],
+        // By default this is a warning but we want it to error.
+        '@typescript-eslint/explicit-module-boundary-types': 2,
+      },
+    },
+    {
+      files: ['test-browser/**/*.js'],
+      parserOptions: {
+        sourceType: 'module',
+      },
+      env: {
+        es6: true,
+        browser: true,
+        es2020: true,
+      },
+    },
+  ],
+};

.gitattributes

@@ -0,0 +1,2 @@
+# Declare files that will always have LF line endings on checkout.
+*.txt eol=lf

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,58 @@
+name: Bug report
+description: File a bug report
+title: '[Bug]: '
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: summary
+    attributes:
+      label: Bug description
+      description: What did you do? What did you expect to happen? What actually happened instead?
+      value: |
+        Steps to reproduce the problem:
+
+        1. …
+    validations:
+      required: true
+  - type: input
+    id: puppeteer-version
+    attributes:
+      label: Puppeteer version
+      description: What version of Puppeteer are you running?
+    validations:
+      required: true
+  - type: input
+    id: node-version
+    attributes:
+      label: Node.js version
+      description: What version of Node.js are you running?
+    validations:
+      required: true
+  - type: input
+    id: npm-version
+    attributes:
+      label: npm version
+      description: What version of npm are you running?
+    validations:
+      required: true
+  - type: dropdown
+    id: operating-system
+    attributes:
+      label: What operating system are you seeing the problem on?
+      multiple: true
+      options:
+        - Linux
+        - macOS
+        - Windows
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. No need for backticks — this automatically gets formatted into code.
+      render: shell

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: General Puppeteer questions
+    url: https://stackoverflow.com/questions/tagged/puppeteer
+    about: For general technical questions or “how to” guidance, please search StackOverflow for questions tagged “puppeteer” or create a new post.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,20 @@
+<!-- Thanks for submitting a pull request! Please provide enough information so that others can review your pull request. -->
+
+**What kind of change does this PR introduce?**
+
+<!-- E.g. a bugfix, feature, refactoring, build related change, etc… -->
+
+**Did you add tests for your changes?**
+
+**If relevant, did you update the documentation?**
+
+**Summary**
+
+<!-- Explain the **motivation** for making this change. What existing problem does the pull request solve? -->
+<!-- Try to link to an open issue for more information. -->
+
+**Does this PR introduce a breaking change?**
+
+<!-- If this PR introduces a breaking change, please describe the impact and a migration path for existing applications. -->
+
+**Other information**

.github/dependabot.yml

@@ -0,0 +1,12 @@
+version: 2
+updates:
+  - package-ecosystem: npm
+    directory: /
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 3
+  - package-ecosystem: github-actions
+    directory: '/'
+    schedule:
+      interval: daily
+    open-pull-requests-limit: 2

.github/release-please.yml

@@ -0,0 +1,4 @@
+releaseType: node
+primaryBranch: main
+handleGHRelease: true
+manifest: true