Gunter Spranz

I had to disable the Typescript error :) Hopefully the author looks into it. ```` // Todo: remove after bug is fixed: https://github.com/mohsinulhaq/react-popper-tooltip/issues/140 // eslint-disable-next-line @typescript-eslint/ban-ts-comment // @ts-ignore ````

There is currently a bug in the preview feature of Vite [Issue 2754](https://github.com/vitejs/vite/issues/2754). As soon as Node and the browser both agree on using HTTP/2 the preview server crashes with...

Ok, that seems reasonable. So these are the options? - Disable compression in vite (for a short term solution, make it configurable with default disabled) - Wait for Express 5...

Hi @dougwilson. At least Fastify and Koa seem to have their own compression module. Fastify offers experimental support for HTTP2. Not sure about Koas HTTP/2 status. I am forced to...

This worked for me: 1. Install @protobuf-ts/proto as extra (direct) dev-dependency: `pnpm i -D @protobuf-ts/protoc` 2. Use pnpm instead of npx/pnpx: `pnpm protoc --ts_out . --proto_path protos protos/msg-readme.proto` 3. For...

I had the same problem and added another line in bluebirds promise.js (line 658) to track the problem down: ` console.log(JSON.stringify(reason, null, 4));` This is the error message I got:...

@mohsinulhaq: Sorry only saw this now :) Yes, the error went away. I am using 4.4.2 now.

I solved my problem in the meanwhile by hacking protoc.exe to generate ES6 modules

I have forked commit a1d8f8f9 of https://github.com/protocolbuffers/protobuf and patched ES6 support. It works for me and sorry, I never bothered to pull master again. Here is a patch: https://gist.github.com/gunters63/3c8798de46fa469e1ce06966df017ca8 If...

Here a link: https://nextcloud.spranz.info/s/A7xHwmrbM6ByTnf The zip-Archiv also contains Linux binaries, but I never tested them.