Ben McCann

Actually, thinking more about this, it's probably better that it live in the image component. If it's returned as output from `imagetools` it will have to be returned for every...

+1 i'd really love to see this in Maven Central

It's not Vite that has a problem with the names, but Node.js. If you use a bundler, you can bundle the files into a proper package. Vite does not bundle...

@robmadole @tagliala I'm happy to rebase this PR when you're ready to merge it. I'm not going to try to keep it up-to-date until you give the go ahead as...

@robmadole I share your frustration with Node.js here! That being said, I don't make the rules and just have to follow them. I've been helping across lots of different packages...

Thanks @robmadole! Let me know when you're ready to merge and I can resolve the merge conflicts then.

This is primarily a client-side library. Distributing it only as CJS would be pure madness ESM works far better with modern frontend development tools in my experience. It lets you...

Yes! It's working for me as well now. Please feel free to close this PR and all the linked issues!

This would be fixed by https://github.com/markedjs/marked/pull/2227/files#diff-a1f849ecb1b5f277935b6443d357e81407d4f53e94dce3668115a64a33b8ef91R10 if we merge that PR

The thing that confuses me is that I think GRPC always takes a `request` object. E.g. in the [HelloWorldSchemaModule](https://github.com/google/rejoiner/blob/master/examples/src/main/java/com/google/api/graphql/examples/helloworld/graphqlserver/HelloWorldSchemaModule.java) example you gave, the call is `client.sayHello(request)`. I'm confused how the...