Replies: 1 comment 2 replies
-
It's not that simple because the babel plugin happens at compile-time, the compiled output differs depending on it. There would need to be some sort of shared config that the runtime tapped into that was prepared at compile time. But the runtime can't drive this without de-opting everything. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
from this issue and this issue
The separated config for delegateEvents in both compile and runtime is not good. We make components library using JSX, but we have to bind half of delegateEvents in its babel config, with the other half of delegateEvents leaving to the app developer to config it at runtime.
I thought for tha babel plugin, it may designate the task of decide how to bind events to the solid library, and let the library decide how to bind events by runtime config.
Beta Was this translation helpful? Give feedback.
All reactions