rob-myers

I'm biased because I want to work purely with the parse-tree. It could be useful to those who want to do their own analysis/transformations/interpreter. Wouldn't it be possible to reconstruct...

I'm trying to understand how you handle brace-expansion. Parsing `{echo,foo,bar}` yields a single `Word` with a single literal. But parsing `{echo,foo,$( echo bar )}` yield a single `Word` with three...

No need. I just wanted a sanity check, thanks.

A new release of the npm module would be great, if possible. Are there any particular breaking changes to be aware of? I will update my typings: > https://github.com/rob-myers/rob-myers.github.io/blob/three-cli/types/mvdan-sh/index.d.ts

I run it in the browser, so web assembly is fine by me. Thanks.

We can also write the function above using JSDoc types. ```tsx /** * JSDoc types lack a non-undefined assertion. * https://github.com/Microsoft/TypeScript/issues/23405#issuecomment-873331031 * * Throws if the supplied value is _undefined_...

I got things working by directly patching `pixi-viewport` and `@pixi/react`, and adapting the above approach. ```json "@pixi/react": "^7.1.1", "pixi-viewport": "^5.0.2", "pixi.js": "^7.3.2", ``` `@pixi/react` patch: ```patch --- a/node_modules/@pixi/react/dist/index.es-dev.js +++ b/node_modules/@pixi/react/dist/index.es-dev.js...