Brian Takita

@littledan @alxhub JS is a Garbage Collected language. With the UI library, an unload event can be listened to unwatch the signal. Outside of a UI library, there is no...

Hi all, I wrote a blog post titled [Signals Proposal Compared to rmemo/WeakRef](https://briantakita.me/posts/signals-proposal-compared-to-rmemo-weak-ref). The blog post explains use cases & follows up @littledan's performance concern brought up on Discord. And...

I filed https://github.com/vanjs-org/mini-van/issues/6 & will move my comments here. The types should allow `undefined` even if `undefined` is ignored in the implementation. If a component has an optional prop, then...

Perhaps a helper function would be a way to get around the impasse? ```ts function cleanProps(props:Object) { for (const key of Object.keys(props)) { if (props[key] === undefined) delete props[key] }...

Sounds good. At least we have a viable solution posted. I'm probably going to use a wrapper `Proxy` around the `van` object with various helpers for now.

It's beneficial for contributors to have an automated test suite that runs before commits. Something like `size-limit` hooks into the test suite to ensure that the gzip size is not...

I'm not concerned either way what tech is used. But just wanted to point out the utility of the DX.

I think the npm script will have to run the build & call size-limit on the build output.

I updated the branch to run size-limit on `public/van-latest.min.js`. The size is `962 B`. `npm test` now runs `(cd ./src; ./publish.sh) && npm run test:size` `publish.sh` did not work on...

Adding the rollup option `{watch: {useChokidar: false}}` fixes the issue