309d8115c3
Replacing the Node EventEmitter with Mitt caused more problems than anticipated for end users due to the API differences and the amount of people who relied on the EventEmitter API. In hindsight this clearly should have been explored more and then released as a breaking v4. This commit rolls us back to the built in Node EventEmitter library which we can release to get everyone back on stable builds. We can then consider our approach to migrating to Mitt and when we do do that we can release it as a breaking change and properly document the migration strategy and approach. |
||
|---|---|---|
| .. | ||
| check_public_api | ||
| preprocessor | ||
| .gitignore | ||
| cli.js | ||
| Message.js | ||
| README.md | ||
| Source.js | ||
DocLint
Doclint is a small program that lints Puppeteer's documentation against Puppeteer's source code.
Doclint works in a few steps:
- Read sources in
lib/folder, parse AST trees and extract public API- note that we run DocLint on the outputted JavaScript in
lib/rather than the source code insrc/. We will do this until we have migratedsrc/to be exclusively TypeScript and then we can update DocLint to support TypeScript.
- note that we run DocLint on the outputted JavaScript in
- Read sources in
docs/folder, render markdown to HTML, use puppeteer to traverse the HTML and extract described API - Compare one API to another
Doclint is also responsible for general markdown checks, most notably for the table of contents relevancy.
Running
npm run doc
Tests
Doclint has its own set of jasmine tests, located at utils/doclint/test folder.
To execute tests, run:
npm run test-doclint