Wasm binary optimization in dfx

[lastmjs]

I’ve been using ic-cdk-optimizer and am attempting to switch over to ic-wasm. These tools are essential for Azle and Kybra, the TypeScript and Python CDKs. One issue of complication that arises when developers try to use Azle and Kybra, is that each CDK must install ic-cdk-optimizer or ic-wasm for the developer, or expect them to install these tools. Requiring any kind of Rust tooling for TypeScript and Python devs is undesirable.

Basically, can we incorporate ic-wasm into the dfx build process somehow, especially so that developers don’t have to independently install ic-wasm?

[paulyoung]

New place for dfx feature requests

Hello everyone! Short version: We now collect dfx feature requests over at sdk/discussions Please upvote features that are important to you We can use the upvotes to prioritise features It’s also ok to request features here on the forum, but I will then create a mirror of the post over at sdk/discussions Longer version: For quite a while now the issues page for dfx was an absolute mess. Old tickets, blue-sky feature discussion, normal feature requests, and actual bug reports were mixed in …

[Severin]

Recorded feature request here.

[lwshang]

Since this merged PR, dfx default to run ic-wasm shrink pass during canister build. No need to install ic-wasm binary.

This feather was included since dfx v0.12.0-beta.3.

[lastmjs]

Does it do that with custom canisters?

[lastmjs]

Looks like it does according to the PR comments. Unfortunately ic-wasm shrink does not shrink the binary as much as ic-cdk-optimizer…so still can’t switch to ic-wasm