Problem

When you run an empty project in WASM using flutter_modular it breaks.

Solution

I believe this issue will be resolved in the Flutter engine itself in the future. It’s likely specific to WASM compilation, as it doesn’t occur on other platforms. Looks like some named params are not working well in WASM, so I recommend to use constructors with positional params of named params.

The injections causing the error in an empty project are internal to flutter_modular. I managed to resolve it by changing the constructors params from positional to named (see the changed files).

For developers

If you want to use named params and you are receiving this error you need to register your dependency like that (only for the dependencies that are returning error in the browser console):

🚫 Before (does not work on WASM)

    i.addSingleton<ModularRouteInformationParser>(ModularRouteInformationParser.new);

✅ After (Works on WASM)

    i.addSingleton<ModularRouteInformationParser>(() {
      return ModularRouteInformationParser(
        getArguments: i(),
        getRoute: i(),
        reportPush: i(),
        setArguments: i(),
        urlService: i(),
      );
    });

When we have it fixed (in Flutter side or in the auto_injector package) this workaround will not be needed anymore.

Checklist

• The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
• I have read the Contributor Guide and followed the process outlined for submitting PRs.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation in docs and added dartdoc comments with ///.
• I have updated/added relevant examples in examples.

Breaking Change

• Yes, this is a breaking change.
• No, this is not a breaking change.

Related Issues

• Closes webassembly bug #975
• Closes BUG - Support for WebAssembly (Wasm) auto_injector#23