Skip to content

Releases: KeithHenry/chromeExtensionAsync

v3.3.2

06 Feb 08:28
137f873
Compare
Choose a tag to compare

Fixed #15, bug calling chrome.identity.getRedirectURL

v3.3.1

05 Feb 08:29
afb804c
Compare
Choose a tag to compare

#10 Fix for changes in chrome.storage that require this to be explicitly bound to the API.

v3.3.0

21 Aug 07:12
97398be
Compare
Choose a tag to compare

Added ES5 support for tool chains that need it.

This adds babel dev dependencies for building the ES5 output, but the core library is the same as v3.2.4

v3.2.4

12 Apr 10:54
Compare
Choose a tag to compare

Added parameter support to executeAsyncFunction and clarifications to docs.

v3.2.2

05 Apr 07:44
Compare
Choose a tag to compare

Refactor of the new chrome.tabs.executeAsyncFunction so that it no longer needs a timer/timeout.

v3.2.1

04 Apr 08:04
Compare
Choose a tag to compare

Typo bugfix, missing () cause setup closure to not execute. Now fixed.

v3.2.0

04 Apr 07:54
Compare
Choose a tag to compare

Added chrome.tabs.executeAsyncFunction to easily execute async functions in the page from an extension. This isn't part of the core API extension and is referenced separately:

<script type="text/javascript" src="execute-async-function.js"></script>

v3.1.2

24 Mar 11:16
Compare
Choose a tag to compare

Added chrome.sockets.tcp, .udp and tcpServer (as chrome.socket is deprecated).

Minor fixes for [] being passed when there are no arguments passed in the callback.

v3.1.0

23 Mar 16:37
Compare
Choose a tag to compare

Added support for multiple-parameter callbacks.
Added lots of additional APIs.
Added TypeScript definitions chrome-extension-async.d.ts

v3.0.0

14 Mar 10:45
Compare
Choose a tag to compare

3.0.0 is a breaking change from v1 and v2: now the original API is wrapped by an identical method that can be called with either old or new syntax.
Callbacks can still be used on the same methods, and will fire before the promise resolves.
Any error thrown inside the callback function will cause the promise to reject.