v0.11.0
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.
Breaking changes
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).
- Convert to object-first convention for use with fast pipe (#77)
- Remove deprecated
Launcher
module (cbf2e30) - Alter
JSHandle.t
andElementHandle.t
to track the type of what they contain (#91) - Reconcile the types of the two
queryObjects
functions (25cda07) - Launch option
ignoreDefaultArgs
now takes the variantPuppeteer.IgnoreDefaultArgs.t
containing a bool or an array of args (cadd87b)
Upgrade instructions:
Change usage of the |>
operator to ->
(or |.
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 ignoreDefaultArgs
you may need to adjust your usage to fix a compile error.
Bug fixes
- Frame.executionContext should return a promise (#87)
- fix: remove t-last wrapper for setBypassCSP (a340d23)
- Fix some issues with Request.continue overrides (5310e36, d422900)
- NOTE: The API of
Request.continue
'soverrides
argument was refactored. While this is technically breaking, the overrides were not previously usable.
- NOTE: The API of
- fix: Response.remoteAddress needs to be a Js.t (2c10aa1)
- Previously this was typed incorrectly.
- Fix
evaluateHandle
return types to make callbacks return handles (370ca6e)
New features
Bindings to new features introduced upstream.