6a0eb7841f
* fix: wider compat TS types and CI checks to ensure correct type defs This PR improves our TS types further to make sure they are usable in a TS environment where ES Modules are the target output. Our use of `export =` is problematic this environment as TypeScript does not allow `export =` to be used and it errors. The fix for the type issues to avoid `export =` is to instead define the functions that you gain access to when you import Puppeteer as top level functions in our `types.d.ts` file. We can do this by declaring them explicitly in `src/node.ts`. These are then rolled into `lib/types.d.ts` at build time. The downside to this is that we have to keep those declarations in sync with the Puppeteer API; should we add a new method to the `Puppeteer` class, we must add it to the `nodes.ts` declarations. However, this could easily be automated by a small script that walks the AST and generates these. I will do that in a follow-up PR, but I consider this low risk given how rarely the very top level API of Puppeteer changes. The nice thing about this approach is we no longer need our script that hacks on changes to `lib/types.d.ts`. To avoid yet more releases to fix issues in one particular TS environment, this PR also includes a suite of example setups that we test on each CI run. Each sample folder contains `good.ts`, which should have no TS errors, and `bad.ts`, which should have some errors. The test first packs Puppeteer into a tar, and then installs it from that tar into each project. This should replicate how the published package behaves when it is installed. We then check that we get no errors on `good.ts`, and the expected errors on `bad.ts`. We have a variety of test projects that cover both TS and JS source code, and CJS and ESM imports and outputs.
151 lines
3.8 KiB
YAML
151 lines
3.8 KiB
YAML
name: run-checks
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
pull_request:
|
|
branches:
|
|
- main
|
|
|
|
jobs:
|
|
linux-main-checks:
|
|
# https://github.com/actions/virtual-environments#available-environments
|
|
runs-on: ubuntu-latest
|
|
strategy:
|
|
matrix:
|
|
# Include all major maintenance + active LTS Node.js versions.
|
|
# https://github.com/nodejs/Release#release-schedule
|
|
node: [10, 12, 14]
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v2
|
|
with:
|
|
fetch-depth: 2
|
|
|
|
- name: Set up Node.js
|
|
uses: actions/setup-node@v1
|
|
with:
|
|
node-version: ${{ matrix.node }}
|
|
|
|
- name: Install dependencies
|
|
run: |
|
|
sudo apt-get install xvfb
|
|
# Ensure both a Chromium and a Firefox binary are available.
|
|
PUPPETEER_PRODUCT=firefox npm install
|
|
npm install
|
|
ls .local-chromium .local-firefox
|
|
|
|
- name: Build
|
|
run: |
|
|
npm run build
|
|
|
|
- name: Run code checks
|
|
run: |
|
|
npm run lint
|
|
npm run generate-docs
|
|
npm run ensure-correct-devtools-protocol-revision
|
|
npm run test-types-file
|
|
|
|
- name: Run unit tests
|
|
env:
|
|
CHROMIUM: true
|
|
run: |
|
|
xvfb-run --auto-servernum npm run unit
|
|
|
|
- name: Run unit tests with coverage
|
|
env:
|
|
CHROMIUM: true
|
|
run: |
|
|
xvfb-run --auto-servernum npm run unit-with-coverage
|
|
xvfb-run --auto-servernum npm run assert-unit-coverage
|
|
|
|
- name: Run unit tests on Firefox
|
|
env:
|
|
FIREFOX: true
|
|
run: |
|
|
xvfb-run --auto-servernum npm run funit
|
|
|
|
- name: Run browser tests
|
|
run: |
|
|
npm run test-browser
|
|
|
|
- name: Test bundling and installation
|
|
env:
|
|
CHROMIUM: true
|
|
run: |
|
|
# Note: this modifies package.json to test puppeteer-core.
|
|
npm run test-install
|
|
# Undo those changes.
|
|
git checkout --force
|
|
|
|
macos:
|
|
# https://github.com/actions/virtual-environments#available-environments
|
|
runs-on: macos-latest
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v2
|
|
with:
|
|
fetch-depth: 2
|
|
|
|
- name: Set up Node.js
|
|
uses: actions/setup-node@v1
|
|
with:
|
|
# Test only the oldest maintenance LTS Node.js version.
|
|
# https://github.com/nodejs/Release#release-schedule
|
|
node-version: 10
|
|
|
|
- name: Install dependencies
|
|
run: |
|
|
# Test platform-specific browser binary fetching for both
|
|
# Chromium and Firefox.
|
|
PUPPETEER_PRODUCT=firefox npm install
|
|
npm install
|
|
ls .local-chromium .local-firefox
|
|
|
|
- name: Build
|
|
run: |
|
|
npm run build
|
|
|
|
- name: Run unit tests
|
|
env:
|
|
CHROMIUM: true
|
|
run: |
|
|
npm run unit
|
|
|
|
windows:
|
|
# https://github.com/actions/virtual-environments#available-environments
|
|
runs-on: windows-latest
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v2
|
|
with:
|
|
fetch-depth: 2
|
|
|
|
- name: Set up Node.js
|
|
uses: actions/setup-node@v1
|
|
with:
|
|
# Test only the oldest maintenance LTS Node.js version.
|
|
# https://github.com/nodejs/Release#release-schedule
|
|
node-version: 10
|
|
|
|
- name: Install dependencies
|
|
run: |
|
|
# Test platform-specific browser binary fetching for both
|
|
# Chromium and Firefox.
|
|
$env:PUPPETEER_PRODUCT='firefox'
|
|
npm install
|
|
Remove-Item Env:\PUPPETEER_PRODUCT
|
|
npm install
|
|
Get-ChildItem -Path .local-chromium,.local-firefox
|
|
|
|
- name: Build
|
|
run: |
|
|
npm run build
|
|
|
|
- name: Run unit tests
|
|
env:
|
|
CHROMIUM: true
|
|
run: |
|
|
npm run unit
|