Hello,

While my focus is on developing Waku, I work on other projects too. Today, I worked on Jotai. A new issue was reported, which is kind of a bug in the core of the library. It's an edge case behavior and, while unexpected, it's usually not a major problem. The issue involves extra remounting behavior, and extra remounts shouldn’t fundamentally break app behavior. It's the same concept as with useEffect: useEffect can invoke effects more than once. Nonetheless, extra remounts are not ideal because we could have heavy tasks in the onMount function, like subscriptions to external services. Now, I found a way to fix it, but it caused an existing test to fail. This fix can lead to the read function running more than once in an edge case. I think it's pretty rare and I don’t consider it a breaking change, but it is a change in behavior. My final thought is that, as we educate people that the read function should be pure and lightweight, reducing onMount invocations is more important, and this makes sense. Therefore, I believe the change should be merged. I just made a patch release recently, so I'm wondering when the next release should be. Maintaining libraries isn't simple.

Happy Hacking.

0 comments

HackDiary#104

HackDiary#103

HackDiary#102

HackDiary#101

HackDiary#100

See all posts from Daishi Kato