I believe that this should be safe to add. @Liamolucko would you mind double-checking me on this?

This doesn't work with --target web, since the default export is already used for init. But it works with all other targets.

I don't particularly like adding target-compatibility caveats like this, but I also can't really imagine a scenario where it's an issue - discovering that you aren't allowed to set the default export on --target web isn't really any weirder than discovering that it got silently renamed to _default.

If we do go ahead with this it'd be nice if the CLI printed a proper error when trying to create a default export on the web target, rather than delaying it until the JS is actually used and throws a 'duplicate default export' error.

If we do go ahead with this it'd be nice if the CLI printed a proper error when trying to create a default export on the web target, rather than delaying it until the JS is actually used and throws a 'duplicate default export' error.

I think that sounds reasonable enough. I'll try to extend my PR with a check for --target weband #[wasm_bindgen(js_name = default)]

I've added a check that throws an error if wasm-bindgen-cli is called with --target web and there exist a exported symbol called "default". I'm notoriously bad at creating good error messages, so feedback is welcome 😆

@daxpedda @Liamolucko Not to be pushy, but is there a chance I can get a new review ?