The version 3.3.0 works. While the latest not.

from marp-cli.

Similar: marp-team/marp-vscode#448

The Chromium browser might be getting stuck while spawning by Puppeteer. What CLI logs will be output if set DEBUG env as puppeteer:*?

set DEBUG=puppeteer:*
marp --pdf slide-deck.md

from marp-cli.

We are temporarily closing this issue until additional information necessary for verification and reproduction is provided. If the problem persists, please reopen this issue with the required information.

from marp-cli.

Same problem here.

Input

slides.md

---
marp: true
---

# hello

Console output

$ DEBUG=puppeteer:*
$ echo $DEBUG         
puppeteer:*
$ marp --pdf slides.md
(node:9589) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[  INFO ] Converting 1 markdown...

It hangs out indefinitely. And it doesn't seem to log more information.

Environment

macOS Sonoma 14.2.1 (23C71)
Node.js v21.4.0
marp-cli v3.4.0

from marp-cli.

Have installed the latest version of Chrome? Recent Puppeteer that the current Marp CLI is using may not compatible with previous Chrome versions due to the change of automation protocol for Chrome (WebDriver BiDi).
https://developer.chrome.com/blog/puppeteer-webdriver-bidi-2023

from marp-cli.

Oh, you are right. I'm not a Chrome user, so my Chrome was still in v108. Upgraded to v120, and now everything is fine. Thanks.

from marp-cli.