Ingvar Stepanyan

Hm from a quick search sounds like the same issue as described in https://forums.powershell.org/t/redirect-stderr-using-tee-object-unexpected-behavior/24264/5.

Yeah that does look increasingly more appealing.

FWIW the idea of https://github.com/wasm-bindgen/wasm-bindgen/issues/4621 is exactly as a replacement for wasm-pack. If we built that linker wrapper, we'd get even better integration with Cargo features (e.g. workspaces) "for free".

> Apart from the whole JS ecosystem integration `wasm-pack` provides I'm not sure what you're referring to there tbh. I don't think it does anything special to JS+Wasm aside from...

If we do want Cargo wrapper, we might as well stick to wasm-pack - @drager asked to transfer it to themselves recently because they were keen on maintaining it -...

> But just the regular output of `wasm-pack build` includes more `.js` files, a `package.json` and more `wasm-bbindgen` doesn't do. `package.json` yes, but there shouldn't be any extra `.js` files.

> I'm talking about [the stuff `wasm-pack pack` does](https://drager.github.io/wasm-pack/book/commands/pack-and-publish.html). These are thin wrappers around `npm pack` / `npm publish`, not very interesting to most users.

Oh yeah I agree, that's why when rustwasm was being split up, we didn't ask for wasm-pack to be moved to this org, but @drager asked for it to be...

@drager Are you still intending to work on wasm-pack? Would you be interested in joining our next maintainer meeting to chat?

Just to reflect some private concerns here: this seems like an extension of new syntax sugar that I know @daxpedda wanted to try and avoid in the core, so I'm...