Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[wasm-merge] Does not print to stdout if `-o` is not specified

Open
#7,397 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
wasm
Domain
cli, compilers

Research direction

Start with the wasm-merge handling for the --output/-o option and compare the behavior when it is omitted with the explicit -o - case. Confirm that the documented default is stdout, then add or update coverage for both invocation forms so the tool prints when no output file is specified.

Written by the indexing model from the issue text.

Description

I finally have a use-case for wasm-merge and trying to use it made me think the tool was broken! (It is not).

It says:

wasm-merge options:
-------------------

  --output,-o                          Output file (stdout if not specified)

However, if you don’t specify -o nothing gets printed. -o - makes it print to stdout as expected. I suspect the default value for this flag is not implemented?

Dominant language
WebAssembly
Stars
8.6k
Forks
885
Avg merge
2d 4h
Merged PRs (30d)
77

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WebAssembly/binaryen

All issues in WebAssembly/binaryen

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.