OJ Kwon

_I_ don't rethrow: it's runtime behavior in emscripten https://github.com/emscripten-core/emscripten/blob/b1a78891c216c98d90057a358731424ab609f22c/src/shell.js#L190 by default. This seems bit interesting since emscripten sets global handler to any rejection, I may try to see and change...

I have similar issues as well on msys2 and back to previous version doesn't rely on `zsh-async`. Problem is in `zsh-async` indeed, internally `zsh-async` uses `zpty` for asynchronous task execution...

@belak I've noticed this prompt module(https://github.com/agkozak/agkozak-zsh-theme) came to across same issue and resolved by having separate async execution path for non-zpty-supported system, looks quite promising. Is it considerable to port...

may related with https://github.com/sorin-ionescu/prezto/issues/1523 as well - support async worker for non-pty compatible environment.

It doesn't seem to create hanging zsh processes, but also git status is not appear as well.

Depends on where https://github.com/vercel/next.js/pull/36790 goes, it may be feasible to close this PR and let user try with published npm plugin instead. I'll leave decision to core team.

This feature is already published as swc experimemtal plugin as well, so anyone can opt in without this PR if someone want to try. I am not sure if this...

The error message you shared explicitly says > that does not exist in this version of Next.js

@mobinni I just created simple bootstrap PR here (https://github.com/paulcbetts/forge-examples/pull/1) , probably you can give those a try. when I tried augury it behaves same as others which showing tab only...

For the opinions / suggestions, please use general discussions https://github.com/swc-project/swc/discussions/5151. For the workaround, please refer https://github.com/swc-project/swc/discussions/5151#discussioncomment-3149154= . This issue itself is an announcement, will be locked to avoid diverging comments...