lsimone

Results 11 comments of lsimone

Ubuntu 17.04 **Webstorm: 2017.2.2** Import Cost: 1.0.5 **Not working**

thanks @pdevito3: we are currently using this lib (thanks @nickdodd79 !) and this would definitely solve our issue.

Same happens to me! @WiXSL codesandbox gives error but if you take its url ( https://gzwqfp.sse.codesandbox.io/#/comments ) you can reproduce it

> UPDATE: I can reproduce it on stackblitz and codesandbox but not locally. I'll keep investigating @WiXSL I could reproduce it locally through these steps: 1. (codesandbox) File > export...

we are having the same problem. We are building a component library that should support IE11 too. I like very much haunted, so I tried to make a PoC and...

> atm im working around it, simply by pre-compiling up haunted before my project's main build step... > eg: > `"compile-haunted": "babel ./node_modules/haunted/lib/*.js --out-dir ./node_modules/haunted/compiled --presets=@babel/preset-env"` so @glomotion you basically...

I'll give it a try. Thank you for sharing!

not yet @shwetajoshi601 . I'd like to solve it, maybe I'll fork because there are other use cases that I would like to handle...like computing destination value from several sources...

[The example](https://partytown.builder.io/tests/integrations/intercom/) does not work in Chrome either. Is there any chance this 5 months ago issue will be taken into account? ![image](https://user-images.githubusercontent.com/3266650/223652697-f703126e-a9c2-48b8-9464-0854e22aa82d.png)

> When importing `@preact/signals-react` into a NextJS app (and possibly other frameworks) it breaks fast refresh in local development. I've created a simple reproduction [here](https://github.com/souporserious/preact-signals-nextjs) that showcases the problem. My...