Joe Pea
Joe Pea
But! There's a way around it, if you also use a class decorator: ```js const decoratedProps = new Set() function classDeco(Class) { const props = [...decoratedProps] decoratedProps.clear() for (const prop...
@falentio Yeah, my syntax idea was not very good. 😄 @pabloalmunia That `Mixer` idea looks like it is on the right track, but here's a [TS playground](https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABMOcAUA3AhgGwFyJZgCeANIhAlAKYAeUBRxAlIgN4BQiFCAznDmoA6HHADmmXOUpga9Zl0QAnalBBKkaVgF4AfIgDsADgCcHAL4cOoSLASIARliWT8hEtKp0G7lu0Uy-IIi4q6est4K3CpqGohaiHqIAIwATADMFlYQOFi8vIgAssQAwrn5-twAAihwiFVOSohI2ogALACsAGxZHIECwqISYNQA7kWl5bxaQmAKHAD0S8srq2sLiKMwUAAWRTC01ErZfFD7h02taEI3ACbUlEpYUHBKvIwkANoAujr6imhqIIALbUWQfMg8CL0CF-RCKbj3R7PV68IQqDBHXjUGYqW4gCA4wEgsFQchI14opRwilPF4uIHUUGycJyKCsAA+HMQjOZZJ5JNkzAA3FZBGdKMCAA5wbG3RLnI5oWrkRoi7JTCZlPK8VKVeqSmVy5oKzo9Sx9PgDELDMZaqapGZzDhAA) showing that the...
# Use Case A library wants to import decorators, and compose them into new ones to export the new ones. For example, for a custom element library, it might do...
I love this pattern, especially that it is a class, and allows subclassing and adding features, already including a dispose method. Imo this should also allow the concept of a...
If in the future we add features using an options object, ```js new Effect(() => {...}, { scheduler: optionalScheduler, // default to single run in next microtask pausable: trueOrFalse, //...
> (Pushing unsubscribe into consumer space, which is common, but prone to memory leaks as everyone makes mistakes) Just like setInterval requires clearInterval or else leak. This is not a...
> > they do you need to dispose of them to avoid memory leaks. > > In templating frameworks, disposal is automatic at the _cell_ or block level, for example:...
> Frameworks do a bunch of stuff. I don't think it's feasible that we provide built-in mechanisms for all of their functionality in one proposal. @littledan We will never cover...
It would be great to have Node.js ESM in the nwjs browser. How would this even be achieved? Seems it needs modifications to (or replacement of) the browser's ESM implementation?
[BUG] DOMElement's reactRoot doesn't need to be removed from parentNode if parent already destroyed.
I'm doing lots of testing. I'll make some PRs soon. :]