Boris Kaul

@krausest No, I don't have a clue why this is happening. ivi doesn't have any type of DOM or js object recycling.

> i guess it's not too clear if these helpers follow React convention No, they don't follow the React convention. `useEffect()` hooks are fired immediately after rendering/updating root subtree is...

Any type of diffing can be implemented with stateful directives https://github.com/localvoid/ivi?tab=readme-ov-file#dynamic-argument-name

Yes, it will be way much faster. And it will be able to run in multiple threads (it is the main reason why deduplicated strings will be unsorted). **EDIT**: Forgot...

Just want to simplify parser, since it already supports `` syntax with any elements. It only affects parsing, when static template is generated, void elements are converted to ``. But...

Brought back void elements parsing. Hope that there won't be any necessary changes in the foreseeable future :) Since oxc is still in development and regularly updated, I am going...

https://github.com/localvoid/ivi/blob/master/tests/compiler/module/data/19-comment/input.js - `` will be parsed as comment. - Expressions inside comments aren't supported.

> is it not possible to support this by retaining any comment nodes containing expressions in the dom? It is possible to just ignore expressions in comments, I just overwhelmed...

Hi, thanks for the tip. > If you consider unifying the plugin architecture, you might want to take a look at https://github.com/unjs/unplugin Unfortunately, ivi compiler has a "whole program optimization"...