Skip to content

Releases: swiftwasm/carton

0.17.0

30 Sep 14:18
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 0.16.1...0.17.0

0.16.1

22 Jul 15:42
Compare
Choose a tag to compare

What's Changed

Full Changelog: 0.16.0...0.16.1

0.16.0

15 Jun 14:46
Compare
Choose a tag to compare

This release adds several enhancements in carton test, and allows you to customize optimization strategy.
One of the notable enhancement is --headless option added in carton test, which runs tests using W3C WebDriver protocol

What's Changed

New Contributors

Full Changelog: 0.15.3...0.16.0

0.15.3

24 May 15:20
Compare
Choose a tag to compare

This release fixes an issue when carton test wouldn't be finished after large number of test suites, and improved HTML 5 compatibility.

Merged pull requests:

0.15.2

23 May 15:08
Compare
Choose a tag to compare

This release fixes an issue when JS entrypoints weren't unpacked during carton test --environment node runs.

Merged pull requests:

0.15.1

23 May 09:55
Compare
Choose a tag to compare

This release fixes an issue when temporary symlinks weren't cleaned up after running carton test --environment node.

Merged pull requests:

0.15.0

20 May 14:38
8130899
Compare
Choose a tag to compare

This release of carton includes enhancements and bugfixes. Namely:

  • Compatibility with JavaScriptKit 0.15.0 and later. The long-standing incompatibility between different versions of carton and JavaScriptKit is resolved now. All version combinations of carton and JavaScriptKit higher than 0.15 should be compatible with each other. This is achieved by supplying JavaScriptKit runtime via SwiftPM resources, instead of embedding within .js entrypoints as we did previously. If you relied on the previous behavior, please open an issue describing your use case.
  • carton test can now run your test suite with Node.js when that is installed. Run it as carton test --environment node to enable this.
  • SwiftPM resources from sub-dependencies of your package are now available on the web server with carton dev and bundled with carton bundle. Resources from each target are still isolated in subdirectories named with \(packageName)_\(targetName).resources format, which is hardcoded by SwiftPM. Resources from the main target you're building are still available at the root path, also accessible via Bundle.main.path(forResource:ofType:) function when you import Foundation (mind the binary size overhead when relying on Foundation). Incorrect paths accessed via Bundle.module are a known issue, which we track as swiftwasm/swift#4573.

Many thanks to @AntonioCandinho, @j-f1, and @kateinoigakukun for contributions!

Closed issues:

  • Re-read supplied index.html on updates (#341)
  • carton dev stops rebuilding/reloading after error (#339)
  • Avoid applying I64ImportTransformer when JS BigInt support is enabled (#326)
  • swjs_create_typed_array error on carton test (#322)
  • Host JSKit entrypoint assets on GH Pages CDN (#317)

Merged pull requests:

0.14.2

30 Apr 10:44
Compare
Choose a tag to compare

This is a bugfix release resolving an issue with JavaScript entrypoint code.

Many thanks to @fjtrujy for the contribution!

Closed issues:

  • Apply clock_res_get patch in all entrypoints (#321)

Merged pull requests:

  • Update SwiftPM dependencies (#319) via @MaxDesiatov
  • Override clock_res_get function from wasmer/wasi-js to fix memory issue (#323) via @fjtrujy

0.14.1

12 Apr 11:58
8a73ca9
Compare
Choose a tag to compare

This is a bugfix release that resolves an issue with carton test introduced in 0.14.0. Many thanks to @SDGGiesbrecht for reporting, and to @kateinoigakukun for fixing it!

Closed issues:

  • 鈥渃arton test鈥 fails to run as of 0.14.0 (#313)

Merged pull requests:

0.14.0

10 Apr 15:49
45ba9f6
Compare
Choose a tag to compare

This release uses SwiftWasm 5.6.0 as the default toolchain. Additionally, issue with rebuilding projects when watching for file changes with carton dev has been fixed. Also, please refer to release details for carton 0.13.0 for more information on new recently introduced command-line flags.

Many thanks to @kateinoigakukun for contributions!

Closed issues:

  • Watcher doesn't see my changes (#295)

Merged pull requests: