2018-06-29 01:48:44 +00:00
|
|
|
test/assets/modernizr.js
|
2017-06-11 08:32:59 +00:00
|
|
|
third_party/*
|
2017-07-31 04:49:04 +00:00
|
|
|
utils/doclint/check_public_api/test/
|
2017-08-26 02:28:49 +00:00
|
|
|
node6/*
|
2017-12-08 00:37:22 +00:00
|
|
|
node6-test/*
|
2018-12-06 19:24:00 +00:00
|
|
|
experimental/
|
2020-04-02 14:25:19 +00:00
|
|
|
lib/
|
2020-04-14 11:08:52 +00:00
|
|
|
/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
|
2020-07-14 15:57:29 +00:00
|
|
|
vendor/
|
2020-07-22 11:14:35 +00:00
|
|
|
web-test-runner.config.mjs
|
fix: wider compat TS types and CI checks to ensure correct type defs (#6855)
* 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.
2021-02-10 12:04:36 +00:00
|
|
|
test-ts-types/
|
2021-08-04 09:00:48 +00:00
|
|
|
website/
|
2021-10-08 13:39:49 +00:00
|
|
|
docs-dist/
|
