spencermize

for my particular usage, i added this to my app's `.postcss` file. ``` /* Fixes https://github.com/saadeghi/daisyui/issues/894 */ .input-group :first-child { @apply !rounded-tl-lg !rounded-bl-lg; } .input-group :last-child { @apply !rounded-tr-lg !rounded-br-lg;...

The only way I've found to manage this so far is to keep an external state and update the entire drawing: ``` webGL.settings.data = geoJSON; webGL.setup().render(); ``` I'd love it...

I'm mostly curious about this issue re: performance. Currently, using Points to map out the same number of 'places' renders much faster than Shapes.  vs  It seems like...

It appears I already (somewhat) posted about this in #24 😄

I've hacked around on this. By adding a parameter such as `clearOnRender` to settings and combining with the `preserveDrawingBuffer` option, I was able to convince Glify to maintain the previous...

Hi, is there any update on this issue? I hate to be a nag, but it's a real performance drag for us.

Update: if I use `"type": "module"` in my `package.json`, the problem disappears. Is that a requirement of Langchain?

You rock - thanks! In the immediate term, we're good with running `"type": "module"`, so we can close this ticket unless you want to keep it open.

I'm having a similar issue - I'm not using it on the frontend, but instead in a Next.js / Webpack backend. I still get the same error: ``` Failed to...

With 53 thumbs and no response, is it perhaps time to consider a community fork? I'd prefer not to go that route, but I also would like to update to...