marp stuck a long time without any output
Closed this issue · 6 comments
Version of Marp Tool
@marp-team/marp-cli v3.4.0 (w/ @marp-team/marp-core v3.9.0)
Operating System
Windows
Environment
- OS version: win10
- Node.js: 20.9
How to reproduce
slider-deck.md
---
theme: uncover
---
# hellomarp --pdf slide-deck.md
# [ INFO ] Converting 1 markdown...Expected behavior
generate pdf
Actual behavior
no response
Additional information
No response
The version 3.3.0 works. While the latest not.
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
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.
Same problem here.
Input
slides.md
---
marp: true
---
# helloConsole 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
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
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.