Skip to content

Releases: swiftwasm/JavaScriptKit

0.8.0

Choose a tag to compare

@MaxDesiatov MaxDesiatov released this 21 Oct 12:46
8ba4135

This release introduces a few enhancements and deprecations. Namely, JSValueConstructible and JSValueConvertible were renamed to ConstructibleFromJSValue and ConvertibleToJSValue respectively. The old names are deprecated, and you should move away from using the old names in your code. Additionally, JavaScriptKit now requires the most recent 5.3 and development toolchains, but thanks to this it no longer uses unsafe flags, which prevented building other libraries depending on JavaScriptKit on other platforms.

The main user-visible enhancement is that now force casts are no longer required in client code. That is, we now allow this

let document = JSObject.global.document
let foundDivs = document.getElementsByTagName("div")

in addition to the previously available explicit style with force unwrapping:

let document = JSObject.global.document.object!
let foundDivs = document.getElementsByTagName!("div").object!

Note that the code in the first example is still dynamically typed. The Swift compiler won't warn you if you misspell names of properties or cast them to a wrong type. This feature is purely additive, and is added for convenience. You can still use force unwraps in your code interfacing with JavaScriptKit. If you're interested in a statically-typed DOM API, we recommend having a look at the DOMKit library, which is currently in development.

Lastly, JSError now conforms to the JSBridgedClass protocol, which makes it easier to integrate with idiomatic Swift code.

Closed issues:

  • Errors building example: undefined symbols (#95)
  • Documentation website is broken (#93)
  • Rename JSValueConstructible and JSValueConvertible (#87)
  • Build fails with the unsafe flags error (#6)

Merged pull requests:

0.7.2

Choose a tag to compare

@j-f1 j-f1 released this 28 Sep 15:03
6e84a70

This is a bugfix release that resolves an issue with the JavaScript runtime being unavailable when installed via NPM.

0.7.1

Choose a tag to compare

@MaxDesiatov MaxDesiatov released this 27 Sep 15:31
29fb15f

This is a bugfix release that resolves an issue with the JavaScript runtime being unavailable when installed via NPM.

Closed issues:

  • 0.7.0 unavailable on NPM (#79)
  • Automatic performance testing (#67)

Merged pull requests:

0.7.0

Choose a tag to compare

@MaxDesiatov MaxDesiatov released this 27 Sep 09:49
42ae818

This release adds multiple new types bridged from JavaScript, namely JSError, JSDate, JSTimer (which corresponds to setTimeout/setInterval calls and manages closure lifetime for you), JSString and JSPromise. We now also have documentation published automatically for the main branch.

Closed issues:

  • TypedArray improvement? (#52)

Merged pull requests:

0.6.0

Choose a tag to compare

@MaxDesiatov MaxDesiatov released this 25 Sep 09:56

This release adds JSTypedArray generic type, renames JSObjectRef to JSObject, and makes JSClosure memory management more explicit.

Closed issues:

  • Support for JS Arrays “holes”, including the test suite (#39)
  • BigInt Support (#29)
  • Separate namespaces for methods and properties? (#27)

Merged pull requests:

0.1.0

0.1.0 Pre-release
Pre-release

Choose a tag to compare

@kateinoigakukun kateinoigakukun released this 09 Mar 04:07
Update package.json