On March 9, 2026 1:38:00 PM GMT+01:00, Jonas Smedegaard <[email protected]> wrote:
>Quoting Fabian Grünbichler (2026-03-09 13:09:29)
>>
>>
>> On March 9, 2026 1:03:38 PM GMT+01:00, Jonas Smedegaard <[email protected]>
>> wrote:
>> >Package: wnpp
>> >Severity: wishlist
>> >Owner: Jonas Smedegaard <[email protected]>
>> >X-Debbugs-Cc: [email protected]
>> >
>> >-----BEGIN PGP SIGNED MESSAGE-----
>> >Hash: SHA512
>> >
>> >* Package name : wasm-bindgen
>> > Version :
>> > Upstream Contact: https://github.com/wasm-bindgen/wasm-bindgen/issues
>> >* URL : https://github.com/wasm-bindgen/wasm-bindgen
>> >* License : Apache-2.0 or Expat
>> > Programming Lang: Rust
>> > Description : high-level interactions between Wasm modules and
>> > JavaScript
>> >
>> > Wasm-bindgen is sort of half polyfill
>> > for features like the component model proposal
>> > and half features for empowering high-level interactions
>> > between JS and wasm-compiled code
>> > (currently mostly from Rust).
>> > More specifically this project allows JS/wasm to communicate
>> > with strings, JS objects, classes, etc,
>> > as opposed to purely integers and floats.
>> > Using wasm-bindgen for example you can define a JS class in Rust
>> > or take a string from JS or return one.
>> >
>> >This will be maintained in the collaborative debian section of salsa,
>> >at <https://salsa.debian.org/debian/wasm-bindgen>.
>>
>> this is already packaged as rust-wasm-bindgen ..
>
>I think you are mistaken.
>
>src:rust-wasm-bindgen covers crate wasm-bindgen.
>
>This will cover crate wasm-bindgen-cli that provided the executable
>wasm-bindgen.
There was no indication in the ITP text that this is what you intend to package
;)
Given that the rest of wasm-bindgen is already maintained by the Rust team, it
would IMHO make sense for -cli to be as well..
Would that work for you as well?
Fabian
