Hung up in some environments while getting from stdin

[yhatt]

I've found some cases that Marp CLI hangs up while getting contents from stdin by using get-stdin module.

• Run executable binary via node -e "require('child_process').exec('./marp')"
• Using Marp CLI via Now deploy environment (yhatt/marp-cli-example avoids this problem by passing the content as stdin)
• Using the exported function in VS Code (It found while working to Marp CLI integration to export PDF marp-vscode#4)

It may be related to sindresorhus/get-stdin#13.

[yhatt]

Hmm, I have read discussion about this, and it seems that there is no correct way to resolve this. 🤔

Marp CLI should be continue to support stdin as like as the regular UNIX application. I think that all we can do for problemed environments is what let user opt out the support for reading stdin.