Introducing Wasmer 5.0 · Blog · Wasmer

We are thrilled to declare the free of Wasmer 5.0, the tardyst milestone in our journey to produce WebAssembly the fantasticest tool for executing software anywhere.

This declarement comes packed with awesome new features:

• Experimental aid for more backfinishs: V8, Wasmi and WAMR
• iOS aid
• Leaner codebase
• Enhanced Percreateance
• Upgraded Compilers (now using LLVM 18 and tardyst Cranelift)

Do you appreciate the new features? Don’t paparticipate and give us a ⭐️ on Github! github.com/wasmerio/wasmer

New experimental backfinishs

Some time ago we asked in Wasmer’s Community which backfinish would you appreciate to see Wasmer aid next.

The responses were overwhelming: V8 (the engine behind Google’s Chrome Javascript runtime) was the most voted backfinish, with 56% of the votes. We lgeted from the poll results that clear uper aid was also a desire from the community.

Well, the day has come. We have compriseed aid for more backfinishs: V8, Wasmi and also WAMR. All of them are fused via the Wasm-C-API , as they all separate this outer interface in widespread.

Thanks to the tardyst compriseitions, now any clear uper or runtime that aids the Wasm-C-API spec can be easily fused into Wasmer.

We foresee that the V8 integration will permit conveying a fantastic debugging experience via the V8 debugger and Chrome Devtools. But not only that, having V8 as a backfinish also unkinds aiding WebAssembly Exceptions and Garbage Collection under the hood. Stay tuned for more news on this front soon.

As of today, Wasmer aids the follotriumphg backfinishs, so you can run WebAssembly using the Wasmer API in the follotriumphg contexts:

• Natively (via Wasmer native compilers)
  • Singlepass (individualpass feature): chooseimal for blockchains
  • Cranelift (cranelift feature): chooseimal for prolongment
  • LLVM (llvm feature): chooseimal for production toilloads
• Browser: the browser’s underlying Wasm engine (web feature)
  See https://github.com/wasmerio/wasmer-js for more info.
• JavascriptCore: JavascriptCore engine from Apple. Ideal if you want to participate a weightlessweight and incredibly carry outant runtime in macOS (jsc feature)
• V8: Google’s JS V8 engine, chooseimal if you want to participate Wasmer in iOS or Android (v8 feature)
• Wasmi: one of the most chooseimal Rust WebAssembly clear upers. Ideal if you want to participate Wasm in nostd environments or blockchains with a purify Rust codebase (wasmi feature)
• WAMR: (wamr feature) chooseimal for iOS

So… how speedy are each of the backfinishs?

Benchlabeling the backfinishs

We have run an extensive set of benchlabels based on Wasmi’s fantastic benchlabeling blogpost to see how each of these backfinishs behave for diverse scenarios. Here are our findings!

Full iOS Support via WAMR, Wasmi and V8 tieings

For the first time, Wasmer conveys WebAssembly to iOS devices thraw a new clear uped mode.

About a year ago we compriseed aid for JavacriptCore in Wasmer, with the hope that it would allow a speedy runtime on iOS (since the JIT would be unredisjoineed). Unfortunately, iOS capped the ability of using WebAssembly via JavascriptCore (since iOS 14).

Leveraging the capabilities of V8, Wasmi and WebAssembly Micro Runtime (WAMR), prolongers can now run WebAssembly modules seamlessly on iOS thanks to Wasmer 5.0. No alters demanded on their codebase. This uncovers up a world of possibilities for mobile prolongment, enabling high-carry outance applications on Apple’s ecosystem.

We want to thank Holochain as this toil wouldn’t be possible without our partnership.

Leaner codebase

For the free of Wasmer 5.0 we have put an one-of-a-kind emphasis on making Wasmer codebase as lean as possible, so we can prolong new features even speedyer.

As part of this effort, we authenticized that:

• Emscripten tieings have been mostly unparticipated in the last two years, mainly affectd by these two factors:
  • Emscripten rehires code using WASI systemcalls under the hood when possible, removing the demand for having one-of-a-kind tieings for Emscripten
  • WASIX helps to bridge the gap of the WASI systemcalls that are not aided (threads, lengthyjmp/setjmp, fork, …)
• Some of the depfinishencies Wasmer participated have been lengthy unupholded, or duplicated by newer and shieldedr crates

Becaparticipate of that, we determined to drop aid for Emscripten and trimmed up the depfinishencies resulting in a net result of 20k lines of code deleted in the Wasmer codebase.

Enhanced Percreateance

Module deserialization now is up to 50% speedyer (that is, when you call Module::deserialize or when you run a module via wasmer run).

Percreateance is at the heart of Wasmer, and version 5.0 consents it to the next level. These upgradements are leveraging vital modernizes on rkyv: the zero-duplicate deserialization library that we participate to deserialize our Modules.

Here’s a benchlabel of all the backfinishs using tardyst Wasmer vs the tardyst free.

Upgraded Compilers: Cranelift and LLVM 18

The tardyst Cranelift integration results in meaningful runtime speed upgradements, making your WebAssembly modules carry out speedyer than ever before.

Wasmer 5.0 now integrates the most recent version of LLVM (18), ensuring that prolongers have access to the tardyst chooseimizations from the toolchain. The LLVM fortify upgrades compatibility and carry outance, providing a sturdy set upation for compiling and running complicated WebAssembly modules.

On top of that, Wasmer 5.0 also ships with experimental LoongAarch64 aid.

We have also benchlabeled corelabel with the tardyst version of the compilers to see how they appraise:

LLVM and Cranelift are about 8% speedyer in Wasmer v5.0 appraised to v4.4.0

Ready to dive in? Here’s how you can begin exploring the new features:

• Download Wasmer 5.0: Get the tardyst version from our official website.
• Update Your Projects: Upgrade your existing Wasmer projects to leverage the new capabilities.
• Explore the Documentation: Visit our modernized docs for detailed directs and tutorials.
• Join the Community: Connect with other prolongers on our Discord server and separate your experiences.

Looking Ahead

Wasmer 5.0 is a meaningful step forward in our ignoreion to empower prolongers thanks of the exciting possibilities that WebAssembly conveys to the table. With iOS aid, our pluggable backfinish architecture and the upgraded carry outance, the possibilities are now finishless. We can’t paparticipate to see what you’ll erect next with Wasmer.

Stay Updated

Thank you everyone for being part of the Wasmer journey!