Add support for changes introduced in Puppeteer 1.9.
See the main commits in #97.
Update to support Puppeteer 1.8 features, fix a number of bugs, and refactor API to be more in line with the direction of the ecosystem by being compatible with fast pipe.
This release brings some major refactoring to convert all functions to the t-first (object-first) convention.
All functions are now compatible with fast pipe syntax (
-> in Reason,
|. in BuckleScript).
ElementHandle.tto track the type of what they contain (#91)
ignoreDefaultArgsnow takes the variant
Puppeteer.IgnoreDefaultArgs.tcontaining a bool or an array of args (cadd87b)
Change usage of the
|> operator to
|. in BS) when applied to bs-puppeteer functions.
Check that use of bs-puppeteer function not using a pipe operator are supplying an instance of the type as their first argument.
Functions which take 1 or no arguments won't require any changes.
If you used
queryObjects, either of the handle types, or launched with
you may need to adjust your usage to fix a compile error.
overridesargument was refactored. While this is technically breaking, the overrides were not previously usable.
evaluateHandlereturn types to make callbacks return handles (370ca6e)
Bindings to new features introduced upstream.
Updates with new features and changes from Puppeteer 1.7.
Bug fixes and new features from Puppeteer 1.6.
Support for Puppeteer 1.5. User-facing API changes are listed below. A couple of very minor breaking changes for consistency and correctness are marked as breaking.
Page.type_()and typeOptions to FrameBase (Can now type into Frames) (840364d)
Support for Puppeteer version 1.3.